_ registry / mcp streamable-http · checked 21m ago

pipehero

https://mcp.pipehero.app

Registry code: c021d6eb617fa4d8

api record

Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.pipehero.app/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pipehero live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is pipehero free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does pipehero have?
25 tools: list_api_proposals, set_long_requests, check_api_drift, replay_request, upsert_api_endpoint, list_tunnels, delete_api_endpoint, send_test_webhook, ….
Is pipehero safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
271ms

last good check

priced tools
0

of 25 tools

_ answered our checks, 90 days 378 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • inspect captured webhooks
  • replay a webhook to localhost
  • document api endpoints
  • run an api endpoint against an environment
  • import an openapi spec
takes → gives
data, code → data
tools
11 reads11 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 25 tools
25 auth-required 25 of 25 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_api_proposals reads auth-required 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • set_long_requests changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subdomain",
        "enabled"
      ],
      "properties": {
        "enabled": {
          "type": "boolean"
        },
        "subdomain": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • check_api_drift reads auth-required 4h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id",
        "tunnel"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "How many recent requests to compare (default 200, max 500)."
        },
        "tunnel": {
          "type": "string",
          "description": "Subdomain of the tunnel whose traffic to compare."
        },
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 20 lines
  • replay_request changes data auth-required never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "subdomain",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        },
        "subdomain": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • upsert_api_endpoint changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id",
        "method",
        "path"
      ],
      "properties": {
        "body": {
          "description": "Example request body (any JSON). null clears it."
        },
        "kind": {
          "enum": [
            "http",
            "event"
          ],
          "type": "string",
          "description": "`event` for a webhook your app sends."
        },
        "name": {
          "type": "string",
          "description": "Short title, e.g. Create a charge. Defaults to METHOD /path."
        },
        "path": {
          "type": "string"
        },
        "folder": {
          "type": "string",
          "description": "Folder name, e.g. Charges."
        },
        "method": {
          "type": "string"
        },
        "params": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "in": {
                "enum": [
                  "path",
                  "query",
                  "header",
                  "body"
                ],
                "type": "string"
              },
              "name": {
                "type": "string"
              },
              "type": {
                "type": "string"
              },
              "required": {
                "type": "boolean"
              },
              "description": {
                "type": "string"
              }
            }
          },
          "description": "Documented fields."
        },
        "headers": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "value"
            ],
            "properties": {
              "name": {
                "type": "string"
              },
              "value": {
                "type": "string"
              }
            }
          }
        },
        "version": {
          "type": "integer"
        },
        "description": {
          "type": "string"
        },
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 95 lines
  • list_tunnels reads auth-required 7h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • delete_api_endpoint changes data auth-required never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        }
      }
    }
    arguments 24 lines
  • send_test_webhook changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subdomain",
        "provider"
      ],
      "properties": {
        "body": {
          "type": "string",
          "description": "Custom JSON body (overrides the template)"
        },
        "event": {
          "type": "string"
        },
        "provider": {
          "type": "string"
        },
        "subdomain": {
          "type": "string"
        }
      }
    }
    arguments 22 lines
  • set_ws_passthrough changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subdomain",
        "enabled"
      ],
      "properties": {
        "enabled": {
          "type": "boolean"
        },
        "subdomain": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • create_api_collection changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string"
        },
        "description": {
          "type": "string"
        }
      }
    }
    arguments 14 lines
  • add_api_example changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id",
        "name",
        "status"
      ],
      "properties": {
        "body": {
          "description": "Example response body (any JSON)."
        },
        "name": {
          "type": "string",
          "description": "e.g. Card declined."
        },
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "status": {
          "type": "integer"
        },
        "headers": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "value"
            ],
            "properties": {
              "name": {
                "type": "string"
              },
              "value": {
                "type": "string"
              }
            }
          }
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "status_text": {
          "type": "string"
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        }
      }
    }
    arguments 57 lines
  • export_api_collection reads auth-required never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "format": {
          "enum": [
            "openapi",
            "postman"
          ],
          "type": "string"
        },
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 18 lines
  • run_api_endpoint changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id",
        "environment"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "variables": {
          "type": "object",
          "description": "Values for {{variables}} the environment doesn't define, e.g. {\"id\": \"ch_123\"}.",
          "additionalProperties": {
            "type": "string"
          }
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "environment": {
          "type": "string",
          "description": "Environment name or id, e.g. local."
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        },
        "confirm_write_to_prod": {
          "type": "boolean"
        }
      }
    }
    arguments 39 lines
  • save_captured_request changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id",
        "tunnel",
        "request_id"
      ],
      "properties": {
        "path": {
          "type": "string"
        },
        "folder": {
          "type": "string",
          "description": "Folder for a newly created endpoint, created by name if missing."
        },
        "method": {
          "type": "string",
          "description": "With path: the endpoint that should receive the example."
        },
        "tunnel": {
          "type": "string",
          "description": "Subdomain of the tunnel that captured the request."
        },
        "request_id": {
          "type": "string",
          "description": "Id of the captured request, from list_requests."
        },
        "endpoint_id": {
          "type": "string",
          "description": "Add the example to this endpoint instead of matching by route. Alternative to method + path."
        },
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 36 lines
  • share_api_collection auth-required never probed

    Share a whole collection: every endpoint in it (including ones added later), with its examples and latest run, read-only and with secrets hidden. Environments are never shown and it can't be exported. Returns the collection's link, which never changes. With no other arguments it stays restricted to the workspace; set `link_access` or `invite` people only when the user asks to share it outside the team. get_api_collection returns the link as `share` once it exists.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "invite": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "email"
            ],
            "properties": {
              "role": {
                "enum": [
                  "viewer",
                  "commenter"
                ],
                "type": "string"
              },
              "email": {
                "type": "string"
              }
            }
          },
          "description": "People to invite by email (at most 10). Each gets an email."
        },
        "link_access": {
          "enum": [
            "restricted",
            "viewer",
            "commenter"
          ],
          "type": "string",
          "description": "Who can open it with just the link. Omit to keep the current setting (restricted for a new share)."
        },
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 42 lines
  • list_api_runs reads auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "limit": {
          "type": "integer",
          "description": "1 to 20."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        }
      }
    }
    arguments 28 lines
  • get_api_collection reads auth-required 4h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_api_endpoint reads auth-required 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        }
      }
    }
    arguments 24 lines
  • import_api_spec changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "format",
        "content"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Name for the new collection."
        },
        "format": {
          "enum": [
            "openapi",
            "postman",
            "har",
            "curl"
          ],
          "type": "string"
        },
        "content": {
          "description": "The document (object or JSON string), or the curl command."
        },
        "collection_id": {
          "type": "string",
          "description": "Add to this collection instead of creating one."
        }
      }
    }
    arguments 29 lines
  • share_api_endpoint auth-required never probed

    Create an endpoint's shareable link and return it. With no other arguments the link stays restricted: workspace members can open it (they sign in), which is enough for a PR or an internal message. Only when the user asks to share it outside the workspace: set `link_access` to `viewer` (anyone with the link can read) or `commenter` (Team plan; commenting asks for sign-in), or `invite` people by email (they get an email and sign in with that address). `restricted` turns the public link off; the URL stays the same. The page is read-only and always hides credentials and secrets.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "invite": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "email"
            ],
            "properties": {
              "role": {
                "enum": [
                  "viewer",
                  "commenter"
                ],
                "type": "string"
              },
              "email": {
                "type": "string"
              }
            }
          },
          "description": "People to invite by email (at most 10). Each gets an email."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "link_access": {
          "enum": [
            "restricted",
            "viewer",
            "commenter"
          ],
          "type": "string",
          "description": "Who can open it with just the link. Omit to keep the current setting (restricted for a new share)."
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        }
      }
    }
    arguments 55 lines
  • list_api_collections reads auth-required 7h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_request reads auth-required 2h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "subdomain",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        },
        "subdomain": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • list_api_monitors reads auth-required 21m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "collection_id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • list_requests reads auth-required 4h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "subdomain"
      ],
      "properties": {
        "subdomain": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_api_share_link auth-required 2h ago

    Get the shareable link of an endpoint (a read-only page with its docs, examples and latest run, secrets hidden), who can open it and who was invited. Use it to put the link in a PR, an issue or a message. Each endpoint has one link that never changes; `shared: false` means it has none yet (see share_api_endpoint).

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection_id"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}."
        },
        "method": {
          "type": "string",
          "description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id."
        },
        "endpoint_id": {
          "type": "string",
          "description": "Id of the endpoint. Alternative to method + path."
        },
        "collection_id": {
          "type": "string",
          "description": "Id from list_api_collections."
        }
      }
    }
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c021d6eb617fa4d8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c021d6eb617fa4d8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c021d6eb617fa4d8/badge.svg)](https://brick.blue/agent/c021d6eb617fa4d8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.