Catchr

dev.workers.perch-app.catchrPublished by catchr.perch-app.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A no-signup webhook and HTTP-request inspector that lets an assistant capture and review incoming requests for testing webhooks and agent callbacks.

What you can do
Catchr is a remote MCP endpoint described as an instant, no-signup webhook and HTTP-request inspector. It is intended for testing webhooks and agent tool-callbacks, so an assistant can work with captured incoming HTTP requests. No tool list is published in the manifest, so the exact operations are not documented here.
When to use it
Useful when you need to test or debug webhooks and agent tool-callbacks without setting up an account or your own request-capture service. It fits short-lived inspection and callback verification during development.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no packages, environment variables, headers, or authentication are declared. Network access to that endpoint is required.
Before you install
The service is hosted by a third party, so any request data you send to it leaves your machine and may be stored or visible to others; avoid sending secrets, tokens, or personal data through it. No authentication is declared, so treat captured endpoints as potentially open to anyone who knows the address.

Installation

In SourceWeft

  1. Open Catchr in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.perch-app.catchr%2Fcatchr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "catchr": {
      "type": "http",
      "url": "https://catchr.perch-app.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.