mcp server
pipehero
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.
Description as published by the maintainer. Source
- version 0.1.0
- active
- workflow automation
active — Registry entry last updated 2026-07-09. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_request(id, subdomain)- Get the full request and response (headers + body) of one captured webhook by id. Required: subdomain, id.
list_requests(subdomain)- List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies. Required: subdomain.
list_tunnels- List the user's Pipehero tunnels and whether each is currently online.
replay_request(id, subdomain)- Replay a captured webhook to the user's localhost (the tunnel CLI must be running). Required: subdomain, id.
send_test_webhook(body, event, provider, subdomain)- Send a generated test webhook to the user's localhost (the tunnel CLI must be running). Provide a `provider` (stripe, github, shopify, clerk, slack, resend, paddle, polar, lemonsqueezy) and optional `event` for a realistic sample payload, or pass a custom JSON `body`. Pro plan required. Required: subdomain, provider.
set_long_requests(enabled, subdomain)- Opt a tunnel into a 120-second ingress timeout instead of the 30-second default — for tool calls that legitimately run long, e.g. an MCP server exposed through the tunnel. Persists on the tunnel; pass enabled: false to revert to the 30-second default. Required: subdomain, enabled.
Last successful function declaration observed on . Source: https://mcp.pipehero.app/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.pipehero.app/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-09 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-09 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.pipehero.app | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | mcp.pipehero.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json