Pipehero MCP server

• add_api_exampleFree

  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.

• check_api_driftFree

  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.

• create_api_collectionwrite actionFree

  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.

• delete_api_endpointwrite actionFree

  Delete an endpoint and its examples. Use when the route no longer exists in the code. Cannot be undone.

• export_api_collectionFree

  Export a collection as an OpenAPI 3.1 or Postman 2.1 document. Handy to read the whole API at once.

• get_api_collectionFree

  Get one collection's folders, endpoints (id, method, path, name, version, example count) and environments (with their variables).

• get_api_endpointFree

  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.

• get_requestFree

  Get the full request and response (headers + body) of one captured webhook by id.

• import_api_specFree

  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.

• list_api_collectionsFree

  List the workspace's API collections (saved endpoints with examples and environments). Start here to find a collection_id.

• list_api_monitorsFree

  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.

• list_api_proposalsFree

  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.

• list_api_runsFree

  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.

• list_requestsFree

  List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies.

• list_tunnelsFree

  List the user's Pipehero tunnels and whether each is currently online.

• replay_requestFree

  Replay a captured webhook to the user's localhost (the tunnel CLI must be running).

• run_api_endpointwrite actionFree

  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.

• save_captured_requestFree

  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.

• send_test_webhookwrite actionFree

  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.

• set_long_requestsFree

  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.

• set_ws_passthroughFree

  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.

• upsert_api_endpointFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 461ms20/20
• Tool poisoning22 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 4 write-action tools with no auth3/15
• Maintenancelast push 4 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 4,460 AI and agents servers

Tools

22

the typical AI and agents server has 6

Tools that change things

18%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote AI and agents server answers 100%

Response time

252 ms

faster than 56% of 2,331 AI and agents servers

Pipehero: common questions

Is Pipehero MCP server safe?

Mostly: it is graded B (80/100). Read the Pipehero safety report

How do I install Pipehero?

It runs remotely at mcp.pipehero.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Pipehero need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Pipehero maintained?

The last commit was 44 days ago (2026-09-21). The latest release is v0.1.0.

Is Pipehero up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Pipehero?

Servers from other publishers that do the same job: agent-device MCP server, Mockserver MCP server and Orcareplay MCP server.

How does Pipehero compare with other AI and agents MCP servers?

safety score 80/100 (higher than 60% of 4,460 AI and agents servers); tools 22 (the typical AI and agents server has 6); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.