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 7 min ago.
claude mcp add catchr --transport http https://catchr.perch-app.workers.dev/mcp{
"mcpServers": {
"catchr": {
"url": "https://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"
}
}
}{
"mcpServers": {
"catchr": {
"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 | 77 ms | 7 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.
HTTP request testing from HTTPBin. No key required.
MCP server for API testing: HTTP requests, cURL generation, health checks.
Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.
Create and control browser sessions for web automation, testing, and AI agent tasks
AI testing agents for web apps — dispatch test runs, crawls, fetch artifacts and status.
A standardized testing harness for MCP servers and agent workflows
Catchr — questions
Answers built from our own checks of this server.