mcpbeat Sign in

Webhook Tester API MCP Server

not responding

Webhook Tester API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
36 ms
Response time
average over 24h
0
Stars
last commit 2 Sep 2026

Webhook Tester API does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add webhook-tester --transport sse https://webhook-tester.api.klymax402.com/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "webhook-tester": {
      "type": "sse",
      "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 36 ms 10 min ago

Alternatives to Webhook Tester API

same job, measured the same way
Settled
by settled

Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports

232 installs/wk 18 tools answering
x402 endpoint checker
by workers-soloearn-x402-seller-kit

Test any x402 paid URL without paying: 402, PAYMENT-REQUIRED, USDC, amounts, payTo, EIP-712, CORS.

1 tools answering
x402 Endpoint Check (Tanod)
by tanod

Check an x402 endpoint before you pay it, then test a payment and follow it to settlement.

3 tools answering
Sendora
by sendora

Sendora's docs and API for coding agents: send test mail, read the log, set up webhooks.

2 824 installs/wk 2 tools answering
Idea Launch
by idea-launch

Validate SaaS and app ideas with real, managed ad tests from your coding agent.

answering
Otterkit
by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

61 installs/wk local only
U
URL Normalizer
by ryuamarines

Normalizes and deduplicates a list of URLs. x402 payment required (testnet USDC, Base Sepolia).

1 tools answering
Multimeter
by mshobeyri

Scaffold, validate, format, and run YAML .mmt API tests. Do not invent syntax.

637 installs/wk local only

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 0 of 91 checks got a reply (0.0%), average response time 36 ms. The bar chart above shows every period we have measured.
The registry lists Webhook Tester API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
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 in the form 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.
Is Webhook Tester API open source?
The code is open source: it is published under the MIT licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at webhook-tester.api.klymax402.com, which runs on its operator's own terms.