Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.workers.perch-app.catchr/catchr

REMOTE · CATCHR.PERCH-APP.WORKERS.DEV

Instant no-signup webhook & HTTP-request inspector for testing webhooks and agent tool-callbacks.

0 this week 18 Trust /100

Last scanned (23 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 29 Aug 26 0
    • Stability: 0.97 → pass security
  • 28 Aug 26 0
    • Stability: pass → 0.97 functional
  • 27 Aug 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://catchr.perch-app.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=perch-app.workers.dev CN=WE1,O=Google Trust Services,C=US 22 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA256 e435da77a35b729a1301edcf7506f15b
SANs: perch-app.workers.dev, *.perch-app.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of catchr.perch-app.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://catchr.perch-app.workers.dev/mcp HTTP error 404
http (plaintext) http://catchr.perch-app.workers.dev/mcp Inconclusive 404
MCP tools · 4 exposed · ~411 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
clear_bin ~47

Delete all captured requests from a bin (the bin stays usable). Requires the bin token.

NameTypeReqDescription
bin_idstringyesThe bin id.
tokenstringyesThe bin token.

No output schema declared.

No examples provided.

create_bin ~66

Create a new no-signup capture bin. Returns a live URL you can point any webhook, callback, or agent tool-callback at, plus a token to read what it captured. No account needed.

NameTypeReqDescription
namestring–Optional label for the bin (max 60 chars).

No output schema declared.

No examples provided.

get_requests ~152

Read the HTTP requests captured by a bin (method, path, query, headers, body), newest first. Set wait to block until a request arrives — ideal for 'trigger then assert' with no polling loop.

NameTypeReqDescription
bin_idstringyesThe bin id returned by create_bin.
limitinteger–Max requests to return (default 20, max 100).
sinceinteger–Only return requests with ts greater than this (ms epoch). Use the ts of the last one you saw.
tokenstringyesThe bin token returned by create_bin.
waitinteger–Seconds to block (max 25) until a request arrives. 0 = return immediately.

No output schema declared.

No examples provided.

set_response ~146

Configure the HTTP response a bin returns to whatever hits its URL — set a status code, content-type and body. Use it to test how your webhook sender / agent handles a 500, a specific JSON reply, etc. Omit or reset to return the default 200. Requires the bin token.

NameTypeReqDescription
bin_idstringyesThe bin id.
bodystring–Response body to return verbatim (max 16KB).
content_typestring–Content-Type header for the response (default application/json).
statusinteger–HTTP status code to return (100-599). Default 200.
tokenstringyesThe bin token.

No output schema declared.

No examples provided.

Install

How do I install the dev.workers.perch-app.catchr/catchr MCP server?

dev.workers.perch-app.catchr/catchr is a hosted endpoint at https://catchr.perch-app.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · catchr.perch-app.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-perch-app-catchr-catchr 'https://catchr.perch-app.workers.dev/mcp'
Common questions

What is the dev.workers.perch-app.catchr/catchr MCP server?

dev.workers.perch-app.catchr/catchr is an MCP server listed in the public MCP registry as dev.workers.perch-app.catchr/catchr. Instant no-signup webhook & HTTP-request inspector for testing webhooks and agent tool-callbacks. This page covers its hosted endpoint (https://catchr.perch-app.workers.dev/mcp).

Is the dev.workers.perch-app.catchr/catchr MCP server safe to use?

dev.workers.perch-app.catchr/catchr scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the dev.workers.perch-app.catchr/catchr MCP server expose?

dev.workers.perch-app.catchr/catchr exposes 4 tools: create_bin, get_requests, set_response, clear_bin. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.

Does the dev.workers.perch-app.catchr/catchr MCP server require authentication?

Its publisher declares no required credentials for dev.workers.perch-app.catchr/catchr. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the dev.workers.perch-app.catchr/catchr MCP server still maintained?

dev.workers.perch-app.catchr/catchr is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.