mcpField
W
Webhook Tester X402

Webhook Tester X402

Remote
github.comDeveloper Tools0Updated 8w ago

About Webhook Tester X402

Webhook Tester X402 is an API and MCP server for testing webhook endpoints, aimed at agents and developers. It sends configurable HTTP requests and returns response, latency, and TLS details, with access billed per call through x402.

Key features

  1. 01Send POST, PUT, PATCH, or DELETE requests
  2. 02Set custom headers and JSON body
  3. 03Inspect response data and status
  4. 04Measure latency and TLS details
  5. 05Pay per call with USDC on Base

Use cases

  1. 01Test webhook integrations
  2. 02Debug API callbacks
  3. 03Check endpoint availability
  4. 04Measure webhook response times

MCP support

Exposes the `api_test_webhook` tool to MCP clients. Calls can also be made over HTTP using x402 micropayments.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://webhook-tester.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Webhook Tester API

MCP Server x402 License: MIT

Test 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.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "webhook-tester": {
      "url": "https://webhook-tester.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

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.

Tools

ToolMethodPathPriceDescription
api_test_webhookPOST/api/test$0.005Send a test request to a webhook URL and analyze the response
api_test_webhook

Use 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

NameTypeRequiredDescription
urlstringyesWebhook URL to test (must be https)
methodstringnoHTTP method: POST, PUT, PATCH, DELETE (default: POST)
headersobjectnoCustom headers as key-value pairs
bodyobjectnoJSON body to send
timeoutnumbernoTimeout 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).

Example agent prompts

  • "Test a webhook endpoint by sending a request with custom headers, body, and method"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.