io.github.pipehero/pipehero
REMOTE · MCP.PIPEHERO.APP · SCANNED SEP 21
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 416 tokens (~59/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 8% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.pipehero/pipehero MCP server?
io.github.pipehero/pipehero is a hosted endpoint at https://mcp.pipehero.app/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 · mcp.pipehero.app
claude mcp add --transport http pipehero-pipehero 'https://mcp.pipehero.app/mcp'
{
"mcpServers": {
"pipehero-pipehero": {
"url": "https://mcp.pipehero.app/mcp"
}
}
} {
"servers": {
"pipehero-pipehero": {
"type": "http",
"url": "https://mcp.pipehero.app/mcp"
}
}
} [mcp_servers.pipehero-pipehero] url = "https://mcp.pipehero.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pipehero-pipehero": {
"type": "remote",
"url": "https://mcp.pipehero.app/mcp",
"enabled": true
}
}
} openclaw mcp add pipehero-pipehero --url 'https://mcp.pipehero.app/mcp' --transport streamable-http
mcp_servers:
pipehero-pipehero:
url: "https://mcp.pipehero.app/mcp" {
"McpServers": {
"pipehero-pipehero": {
"Transport": "http",
"Url": "https://mcp.pipehero.app/mcp"
}
}
} assistant mcp add pipehero-pipehero -t streamable-http -u 'https://mcp.pipehero.app/mcp'
{
"mcpServers": {
"pipehero-pipehero": {
"type": "http",
"url": "https://mcp.pipehero.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 0
- Schema quality: 334 → 416 ▼ functional
- Server version: 0.1.8 → 0.1.12 functional
- New tool “set_ws_passthrough” functional
- 12 Aug 26 0
- Schema quality: 50 → 55 ▼ functional
- Server version: 0.1.3 → 0.1.8 functional
- New tool “set_long_requests” 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
- 5 Aug 26 0
- Server version: 0.1.2 → 0.1.3 functional
- 31 Jul 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
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 21 Sept 2026 · Probed https://mcp.pipehero.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pipehero.app | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 862c8e2fad24840b0efbbd975d1d9d23 |
| SANs: pipehero.app, *.pipehero.app | ||||||
| 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 mcp.pipehero.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pipehero.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.pipehero.app/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.pipehero.app/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.pipehero.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.pipehero.app/mcp |
| Authorisation server | https://mcp.pipehero.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pipehero.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pipehero.app/mcp | HTTPS enforced | 301 | https://mcp.pipehero.app/mcp |
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 →
get_request ~41
Get the full request and response (headers + body) of one captured webhook by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| subdomain | string | yes | – |
No output schema declared.
No examples provided.
list_requests ~38
List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies.
| Name | Type | Req | Description |
|---|---|---|---|
| subdomain | string | yes | – |
No output schema declared.
No examples provided.
list_tunnels ~22
List the user's Pipehero tunnels and whether each is currently online.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
replay_request ~39
Replay a captured webhook to the user's localhost (the tunnel CLI must be running).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| subdomain | string | yes | – |
No output schema declared.
No examples provided.
send_test_webhook ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Custom JSON body (overrides the template) |
| event | string | – | – |
| provider | string | yes | – |
| subdomain | string | yes | – |
No output schema declared.
No examples provided.
set_long_requests ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| subdomain | string | yes | – |
No output schema declared.
No examples provided.
set_ws_passthrough ~82
Opt a tunnel into WebSocket passthrough, so an application-level WebSocket connection (e.g. a mobile/web app's own realtime feature) can be relayed to your localhost. Pro/Team plan required to enable; pass enabled: false to disable on any plan.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| subdomain | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.pipehero/pipehero MCP server?
io.github.pipehero/pipehero is an MCP server listed in the public MCP registry as io.github.pipehero/pipehero. Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost. This page covers its hosted endpoint (https://mcp.pipehero.app/mcp).
Is the io.github.pipehero/pipehero MCP server safe to use?
io.github.pipehero/pipehero scores 84 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 io.github.pipehero/pipehero MCP server expose?
io.github.pipehero/pipehero exposes 7 tools: list_tunnels, list_requests, get_request, replay_request, send_test_webhook, and 2 more. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.
Does the io.github.pipehero/pipehero MCP server require authentication?
Yes. io.github.pipehero/pipehero asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.pipehero/pipehero MCP server still maintained?
io.github.pipehero/pipehero is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.