mcpbeat

Webhook Tester API MCP Server

io.github.Br0ski777/webhook-tester
answering

Webhook Tester API is answering right now. Last checked 4 min ago. It exposes 1 tools. Last commit 19 Jul 2026.

Test webhook endpoints — send requests, measure latency, validate responses. x402 micropayment.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
35 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add webhook-tester --transport http https://webhook-tester.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "webhook-tester": {
      "url": "https://webhook-tester.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.webhook-tester]
url = "https://webhook-tester.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "webhook-tester": {
      "url": "https://webhook-tester.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "webhook-tester": {
      "url": "https://webhook-tester.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

api
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. Returns: 1. statusCode 2. responseBody (parsed JSON or text) 3. responseHeaders (key-value map) 4. latency in ms 5. tlsInfo (protocol, cipher) 6. method used 7. requestSize and responseSize in bytes. Example output: {"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} Use this FOR testing webhook integrations, debugging API callbacks, validating endpoint availability, and measuring webhook response times. Do NOT use for web scraping -- use web_scrape_to_markdown instead. Do NOT use for screenshot capture -- use capture_screenshot instead. Do NOT use for HTTP header security audit -- use network_analyze_headers instead.

Endpoints

URLTransportStateLatencyChecked
https://webhook-tester.api.klymax402.com/mcp sse answering 22 ms 4 min ago

Webhook Tester API — questions

Answers built from our own checks of this server.

What can Webhook Tester API do?
It exposes 1 tools, read directly from the server on our last check. Among them: api_test_webhook. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Webhook Tester API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 35 ms. The bar chart above shows every period we have measured.
How do I connect Webhook Tester API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Webhook Tester API need an API key?
No. Webhook Tester API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Webhook Tester API?
It answers our handshake in 35 ms on average, which is faster than 98% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Webhook Tester API open source?
Yes — it is published under the MIT licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.