pipehero MCP server
io.github.pipehero/pipeheropipeherostreamable-httpv0.1.0Scanned
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.
25 tools: 4 can delete or cancel things, 10 change things and 11 only read.
- Reads private data · 3
- Reads text others write · 5
- Can send data out · 1
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the pipehero MCP server can do
The pipehero MCP server is published by the GitHub account pipehero. It has 25 tools. It can delete or cancel things (4 tools: replay_request, send_test_webhook, delete_api_endpoint and run_api_endpoint) and create or change data (10 tools: set_long_requests, set_ws_passthrough, create_api_collection, upsert_api_endpoint and 6 more). 11 tools only read.
3 tools read private data (get_api_collection, check_api_drift and get_api_share_link); 5 tools bring in text other people can write (replay_request, send_test_webhook, run_api_endpoint and 2 more); 1 tool can send data out of your system (send_test_webhook). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
25 tools
Deletes or cancels 4Claude Code: deny
delete_api_endpointDelete an endpoint and its examples.No findings
Why it is in this group
- The name "delete_api_endpoint" says "delete": a word for removing or ending something.
- The description says "Cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete an endpoint and its examples. Use when the route no longer exists in the code. Cannot be undone.
Annotations the server declares
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Delete an API endpoint
replay_requestReplay a captured webhook to the user's localhost (the tunnel CLI must be running).Reads text others writeNo findings
Why it is in this group
- The name "replay_request" says "request": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Replay a captured webhook to the user's localhost (the tunnel CLI must be running).
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Replay a webhook
run_api_endpointSend an endpoint against an environment and return the real response (status, headers, body up to 20 KB).Reads text others writeNo findings
Why it is in this group
- The name "run_api_endpoint" says "run": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Send an endpoint against an environment and return the real response (status, headers, body up to 20 KB). A `local` environment goes through the user's tunnel to their localhost (the CLI must be running); staging/prod are sent from Pipehero's cloud (Pro/Team) to public addresses only. Sending to a `prod` environment with a write method needs confirm_write_to_prod: true, which you should only pass after the user agrees. Use it to check that the code you wrote behaves as documented.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Run an API endpoint
send_test_webhookSend a generated test webhook to the user's localhost (the tunnel CLI must be running).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_test_webhook" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_test_webhook" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Send a test webhook
Changes things 10Claude Code: ask
add_api_exampleSave a response example on an endpoint (for instance the 402 your handler returns for a declined card).No findings
Why it is in this group
- The name "add_api_example" says "add": a word for a change.
Description, as the server wrote it Save a response example on an endpoint (for instance the 402 your handler returns for a declined card). Replaces the example with the same name, so it is safe to repeat.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Add a response example
create_api_collectionCreate an empty API collection.No findings
Why it is in this group
- The name "create_api_collection" says "create": a word for a change.
Description, as the server wrote it Create an empty API collection. Prefer import_api_spec when there is an OpenAPI file, and upsert_api_endpoint to fill it from the code.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create an API collection
export_api_collectionExport a collection as an OpenAPI 3.1 or Postman 2.1 document.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Export a collection as an OpenAPI 3.1 or Postman 2.1 document. Handy to read the whole API at once.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Export an API collection
import_api_specImport an OpenAPI 3.x document (as JSON), a Postman v2.x collection (JSON) or a curl command into a new collection, or into `collection_id`.1 finding
Why it is in this group
- The name "import_api_spec" says "import": a word for a change.
Findings
- Info
The description mentions "Credentials".
What this check looks forMatched text
description: "...ing, and plan limits are checked first. Credentials are never imported (they become variabl..."
Description, as the server wrote it Import an OpenAPI 3.x document (as JSON), a Postman v2.x collection (JSON) or a curl command into a new collection, or into `collection_id`. All or nothing, and plan limits are checked first. Credentials are never imported (they become variables). Convert YAML to JSON before sending.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Import an API spec
save_captured_requestDocument a real request captured by a tunnel (get its id from list_requests).1 finding
Why it is in this group
- The name "save_captured_request" says "save": a word for a change.
Findings
- Info
The description mentions "Credentials".
What this check looks forMatched text
description: "...n endpoint is created from the request. Credentials, cookies and signatures are replaced by..."
Description, as the server wrote it Document a real request captured by a tunnel (get its id from list_requests). If an endpoint already covers the route, the response is added to it as an example; otherwise an endpoint is created from the request. Credentials, cookies and signatures are replaced by {{variables}} and only JSON bodies are kept. A response already saved as an example is not duplicated. Use it to document webhooks and calls you have only seen in traffic.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Save a captured request as docs
set_long_requestsOpt a tunnel into a 120-second ingress timeout instead of the 30-second default — for tool calls that legitimately run long, e.g.No findings
Why it is in this group
- The name "set_long_requests" says "set": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Set extended request timeout
set_ws_passthroughOpt a tunnel into WebSocket passthrough, so an application-level WebSocket connection (e.g.No findings
Why it is in this group
- The name "set_ws_passthrough" says "set": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Set WebSocket passthrough
upsert_api_endpointDocument an endpoint: creates it, or updates the existing one for the same method + path.No findings
Why it is in this group
- The name "upsert_api_endpoint" says "upsert": a word for a change.
Description, as the server wrote it Document an endpoint: creates it, or updates the existing one for the same method + path. Use it whenever you add or change a route in the code, so the docs stay true. Only the fields you send change. `path` may use :id, {id} or {{id}} for variables. `folder` is created by name if missing. Send `version` (from get_api_endpoint) to avoid overwriting a teammate's edit; a stale version is rejected.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Create or update an API endpoint
Only reads 11Show 11 read-only tools
check_api_driftCompare a collection's docs with the real traffic a tunnel captured (Pro/Team).Reads private dataNo findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
What it can reach
- private-dataThe description's first sentence says "compare" and "doc": it reads documents.
Description, as the server wrote it Compare a collection's docs with the real traffic a tunnel captured (Pro/Team). Returns routes nobody documented, status codes with no example, response or request fields missing from every example (or with another type), undocumented query parameters, and documented fields that never appear. Each finding includes `request_id` of the newest request that shows it: pass it to save_captured_request to add it to the docs, or fix the docs with upsert_api_endpoint and add_api_example. Use it to find out what drifted after a code change.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Check API docs against real traffic
get_api_collectionGet one collection's folders, endpoints (id, method, path, name, version, example count) and environments (with their variables).Reads private dataNo findings
Why it is in this group
- The name "get_api_collection" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "folder": it reads files.
Description, as the server wrote it Get one collection's folders, endpoints (id, method, path, name, version, example count) and environments (with their variables).
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Get an API collection
get_api_endpointGet one endpoint in full: description, parameters, headers, request body, saved response examples and its current `version`.No findings
Why it is in this group
- The name "get_api_endpoint" says "get": a word for reading.
Description, as the server wrote it Get one endpoint in full: description, parameters, headers, request body, saved response examples and its current `version`. Identify it by endpoint_id or by method + path.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Get an API endpoint
get_requestGet the full request and response (headers + body) of one captured webhook by id.No findings
Why it is in this group
- The name "get_request" says "get": a word for reading.
Description, as the server wrote it Get the full request and response (headers + body) of one captured webhook by id.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Get a captured request
list_api_collectionsList the workspace's API collections (saved endpoints with examples and environments).No findings
Why it is in this group
- The name "list_api_collections" says "list": a word for reading.
Description, as the server wrote it List the workspace's API collections (saved endpoints with examples and environments). Start here to find a collection_id.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List API collections
list_api_monitorsSee which endpoints of a collection are checked on a schedule (Pro/Team monitors) and how they are doing: state (healthy, failing, blip, paused, waiting), the last check with its s…No findings
Why it is in this group
- The name "list_api_monitors" says "list": a word for reading.
Description, as the server wrote it See which endpoints of a collection are checked on a schedule (Pro/Team monitors) and how they are doing: state (healthy, failing, blip, paused, waiting), the last check with its status, latency and error, and since when it has been failing. Use it to find out what is broken in staging or production, then read the endpoint and its code. Read-only: people decide what to monitor.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List API monitors
list_api_proposalsSee what happened to the changes you proposed.No findings
Why it is in this group
- The name "list_api_proposals" says "list": a word for reading.
Description, as the server wrote it See what happened to the changes you proposed. Some workspaces review AI changes: your write tools then answer `pending_review` and change nothing until a teammate approves. This lists the latest proposals with their status (pending, approved, rejected with the reviewer's reason, or failed with why) so you can tell whether a change went through.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List proposed API changes
list_api_runsRecent runs of an endpoint (newest first, default 5): who/what was sent and what came back.No findings
Why it is in this group
- The name "list_api_runs" says "list": a word for reading.
Description, as the server wrote it Recent runs of an endpoint (newest first, default 5): who/what was sent and what came back. Use to see what happened the last time it was run.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List recent runs
list_requestsList recent webhooks/requests captured for a tunnel.No findings
Why it is in this group
- The name "list_requests" says "list": a word for reading.
Description, as the server wrote it List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List captured requests
list_tunnelsList the user's Pipehero tunnels and whether each is currently online.No findings
Why it is in this group
- The name "list_tunnels" says "list": a word for reading.
Description, as the server wrote it List the user's Pipehero tunnels and whether each is currently online.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
- title: List tunnels
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
15 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__pipehero__send_test_webhook"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 14
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.pipehero.app/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp.pipehero.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 14 tools that change things (4 destructive, 10 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.pipehero.app/mcp: tools/list returned 25 tools to an anonymous client, including replay_request (destructive), send_test_webhook (destructive), delete_api_endpoint (destructive), run_api_endpoint (destructive), set_long_requests (write) and 9 more
Posture changes
- Oct 29, 2026
- Protocol version: 2024-11-05 to 2025-06-18
Findings
Matches of fixed checks, with the text they matched.
- Infoimport_api_spec
The description mentions "Credentials".
What this check looks forMatched text
description: "...ing, and plan limits are checked first. Credentials are never imported (they become variabl..."
The description mentions "Credentials".
What this check looks forMatched text
description: "...n endpoint is created from the request. Credentials, cookies and signatures are replaced by..."
The description mentions "credentials".
What this check looks forMatched text
description: "...The page is read-only and always hides credentials and secrets."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools18 changed.~18 changedView diff
- Changed:add_api_exampleChanges thingsinputSchema
- Changed:check_api_driftOnly readsinputSchema
- Changed:create_api_collectionChanges thingsinputSchema
- Changed:export_api_collectionChanges thingsinputSchema
- Changed:get_api_collectionOnly readsinputSchema
- Changed:get_requestOnly readsinputSchema
- Changed:import_api_specChanges thingsinputSchema
- Changed:list_api_monitorsOnly readsinputSchema
- Changed:list_api_runsOnly readsinputSchema
- Changed:list_requestsOnly readsinputSchema
- Changed:replay_requestDeletes or cancelsinputSchema
- Changed:run_api_endpointDeletes or cancelsinputSchema
- Changed:save_captured_requestChanges thingsinputSchema
- Changed:send_test_webhookDeletes or cancelsinputSchema
- Changed:set_long_requestsChanges thingsinputSchema
- Changed:set_ws_passthroughChanges thingsinputSchema
- Changed:share_api_collectionChanges thingsinputSchema
- Changed:upsert_api_endpointChanges thingsinputSchema
PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18.View diff
- Protocol version: 2024-11-05 to 2025-06-18
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pipehero https://mcp.pipehero.app/mcpclaude mcp add --transport http pipehero https://mcp.pipehero.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pipehero__list_tunnels",
"mcp__pipehero__list_requests",
"mcp__pipehero__get_request",
"mcp__pipehero__list_api_collections",
"mcp__pipehero__get_api_collection",
"mcp__pipehero__get_api_endpoint",
"mcp__pipehero__list_api_monitors",
"mcp__pipehero__list_api_proposals",
"mcp__pipehero__check_api_drift",
"mcp__pipehero__get_api_share_link",
"mcp__pipehero__list_api_runs"
],
"ask": [
"mcp__pipehero__set_long_requests",
"mcp__pipehero__set_ws_passthrough",
"mcp__pipehero__create_api_collection",
"mcp__pipehero__upsert_api_endpoint",
"mcp__pipehero__add_api_example",
"mcp__pipehero__import_api_spec",
"mcp__pipehero__export_api_collection",
"mcp__pipehero__save_captured_request",
"mcp__pipehero__share_api_endpoint",
"mcp__pipehero__share_api_collection"
],
"deny": [
"mcp__pipehero__replay_request",
"mcp__pipehero__send_test_webhook",
"mcp__pipehero__delete_api_endpoint",
"mcp__pipehero__run_api_endpoint"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pipehero. Review it before you use it.
Capability tags behind 8 rules
- mcp__pipehero__replay_request untrusted-input
- mcp__pipehero__send_test_webhook untrusted-input, outbound
- mcp__pipehero__get_api_collection private-data
- mcp__pipehero__run_api_endpoint untrusted-input
- mcp__pipehero__check_api_drift private-data
- mcp__pipehero__get_api_share_link private-data
- mcp__pipehero__share_api_endpoint untrusted-input
- mcp__pipehero__share_api_collection untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.pipehero/pipehero/verify?hash=28c088b26debb826b5204beaa92a3e687829b4a69bf4e155311e34bad64d4a2f" | jq -e '.changed == false'Pinned hash 28c088b26deb, from Nov 20, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.pipehero/pipehero/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.pipehero/pipehero)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:43 UTC.
pipehero MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the pipehero MCP server safe?
- No scan can promise that. What its definitions show: 25 tools, 14 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the pipehero MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: replay_request, send_test_webhook, delete_api_endpoint and run_api_endpoint.
Can the pipehero MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the pipehero MCP server have?
- 25 tools: 4 destructive, 10 write, 11 read. replay_request, send_test_webhook, delete_api_endpoint, run_api_endpoint, set_long_requests, set_ws_passthrough, create_api_collection, upsert_api_endpoint and 17 more.
Does the pipehero MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the pipehero MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_test_webhook.
Has the pipehero MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.