Webhook Tester API
Pay-per-call MCP server that sends test requests to webhook endpoints and reports latency
- Pricing
- Paid
- Platforms
- API, CLI
- Runs
- Remotely
- Version
- 1.1.0
- Listing updated
- today
Similar MCP servers
About Webhook Tester API
Webhook Tester API is a paid MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
The server sends POST, PUT, PATCH or DELETE requests to an HTTPS webhook URL with custom headers and a JSON body, then returns the status code, response body, round-trip latency and TLS details as JSON. The README describes it as one tool within the klymax402 marketplace of x402 micropayment APIs.
Each call is billed in USDC on Base L2 through the x402 protocol, so there is no API key or account to create. The README lists a per-call price of $0.005 for the webhook test tool. Clients connect over SSE at the MCP endpoint, or can call the HTTP route directly and handle the 402 payment challenge.
It suits developers and agents debugging callback integrations, checking that an endpoint is reachable, or comparing response times. The README says it is not meant for web scraping, screenshots or header security audits, and points to other tools for those jobs.
Install
Run in a terminal
claude mcp add --transport sse webhook-tester https://webhook-tester.api.klymax402.com/mcpAdd to Settings → Connectors → Add custom connector
https://webhook-tester.api.klymax402.com/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"webhook-tester": {
"url": "https://webhook-tester.api.klymax402.com/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"webhook-tester": {
"type": "sse",
"url": "https://webhook-tester.api.klymax402.com/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"webhook-tester": {
"serverUrl": "https://webhook-tester.api.klymax402.com/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"webhook-tester": {
"type": "sse",
"url": "https://webhook-tester.api.klymax402.com/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (1)
Taken from the project documentation; the running server may differ.
- api_test_webhook
- Send a test request to a webhook URL and analyze the response
What it does
- Custom request sending
- Sends webhook test requests with a chosen HTTP method, custom headers and a JSON body.
- Latency and TLS reporting
- Returns response latency along with TLS protocol and cipher information for the endpoint.
- Configurable timeout
- Lets the caller set a request timeout up to 30 seconds, defaulting to 10.
- Pay-per-call access
- Charges per request in USDC on Base via x402, with no API key or signup needed.
- MCP and HTTP access
- Reachable as an MCP server over SSE or as a plain HTTP endpoint for x402-aware clients.
Good for
- Debugging a webhook callback that is failing or timing out
- Checking whether a third-party endpoint responds to a test payload
- Measuring webhook response times across different methods
- Letting an AI agent verify an HTTPS callback URL before relying on it
Pricing
Paid
Pay-per-call via x402, $0.005 per webhook test request in USDC on Base
Webhook Tester API FAQ
What HTTP methods can it send?
The tool accepts POST, PUT, PATCH and DELETE, with POST as the default.
Does it need an API key?
No. The README says it uses x402 pay-per-call payments in USDC on Base, with no API key, signup or rate-limit wall.
What is the maximum timeout?
The timeout parameter defaults to 10 seconds and can be set up to 30 seconds.
Does it only accept HTTPS URLs?
The README states the webhook URL must be https.
Is Webhook Tester API free?
No. Webhook Tester API is a paid product.
How do I add Webhook Tester API to Claude Code?
Run this command in your terminal: claude mcp add --transport sse webhook-tester https://webhook-tester.api.klymax402.com/mcp
What are the best alternatives to Webhook Tester API?
The closest alternatives to Webhook Tester API are x402 Tool Shop, GeekVault, Hooklistener, MoneyTools x402 Status & MCP Check and MCP.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.