Reach for this when you need to validate webhook integrations without spinning up your own infrastructure. It connects to a hosted endpoint at webhook-tester.api.klymax402.com and runs over SSE transport. You can fire test requests at webhook URLs, measure response latency, and validate payloads coming back. The x402 micropayment integration suggests it's metered usage, though the GitHub repo doesn't expose implementation details beyond TypeScript source. Useful for debugging third-party webhook configs or load testing callback handlers before you wire them into production systems.
Public tool metadata for what this MCP can expose to an agent.
api_test_webhookUse this when you need to test a webhook endpoint by sending a request with custom headers, body, and method. Returns full response data in JSON. Returns: 1. statusCode 2. responseBody (parsed JSON o5 paramsUse this when you need to test a webhook endpoint by sending a request with custom headers, body, and method. Returns full response data in JSON. Returns: 1. statusCode 2. responseBody (parsed JSON o
urlstringbodyobjectmethodstringheadersobjecttimeoutnumberTest webhook endpoints -- send POST/PUT/PATCH/DELETE with custom headers and payloads. Measure latency and TLS. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"webhook-tester": {
"url": "https://webhook-tester.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://webhook-tester.api.klymax402.com/api/test" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
api_test_webhook | POST | /api/test | $0.002 | Send a test request to a webhook URL and analyze the response |
api_test_webhookUse this when you need to test a webhook endpoint by sending a request with custom headers, body, and method. Returns full response data in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
url | string | yes | Webhook URL to test (must be https) |
method | string | no | HTTP method: POST, PUT, PATCH, DELETE (default: POST) |
headers | object | no | Custom headers as key-value pairs |
body | object | no | JSON body to send |
timeout | number | no | Timeout in seconds (default: 10, max: 30) |
Example response:
{"url":"https://hooks.example.com/callback","method":"POST","statusCode":200,"responseBody":{"received":true},"latency":142,"tlsInfo":{"protocol":"TLSv1.3","cipher":"AES-256-GCM"},"requestSize":256,"responseSize":48}
When to use: testing webhook integrations, debugging API callbacks, validating endpoint availability, and measuring webhook response times.
Not for: web scraping (use web_scrape_to_markdown), screenshot capture (use capture_screenshot), HTTP header security audit (use network_analyze_headers).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
makafeli/n8n-workflow-builder
node2flow/n8n-management
danishashko/make-mcp
lukisch/n8n-manager-mcp
io.github.us-all/airflow