Catchr is listed as active in the registry but did not answer our last check. It exposes 4 tools.
Instant no-signup webhook & HTTP-request inspector for testing webhooks and agent tool-callbacks.
Catchr 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.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
claude mcp add catchr --transport http https://catchr.perch-app.workers.dev/mcphttps://catchr.perch-app.workers.dev/mcp[mcp_servers.catchr]
url = "https://catchr.perch-app.workers.dev/mcp"{
"mcpServers": {
"catchr": {
"url": "https://catchr.perch-app.workers.dev/mcp"
}
}
}{
"servers": {
"catchr": {
"type": "http",
"url": "https://catchr.perch-app.workers.dev/mcp"
}
}
}Available tools 4
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
create_bin
clear_bin
get_requests
set_response
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://catchr.perch-app.workers.dev/mcp | streamable-http | answering | 79 ms | 14 min ago |
Alternatives to Catchr
same job, measured the same wayAnonymous webhook capture, inspection, waiting, and response configuration for AI agents.
Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.
Sendora's docs and API for coding agents: send test mail, read the log, set up webhooks.
HTTP request testing from HTTPBin. No key required.
Free agent tools, no sign-in: browser flows, test inboxes, web extract, site and domain checks.
Webhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.
MCP server for API testing: HTTP requests, cURL generation, health checks.
Transactional email for coding agents: send, test, verify domains, webhooks, logs.
Catchr — questions
Answers built from our own checks of this server.