Home / MCP registry index / io.github.pipehero/pipehero

io.github.pipehero/pipehero

io.github.pipehero/pipehero in the official MCP registry. Endpoint https://mcp.pipehero.app/mcp. Source: github.com/pipehero/pipehero-mcp.

The registry describes it as: Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.

We read its 25 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http pipehero https://mcp.pipehero.app/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "pipehero": {
      "url": "https://mcp.pipehero.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"pipehero","type":"http","url":"https://mcp.pipehero.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_tunnels list_requests get_request replay_request send_test_webhook set_long_requests set_ws_passthrough list_api_collections get_api_collection get_api_endpoint create_api_collection upsert_api_endpoint add_api_example delete_api_endpoint import_api_spec export_api_collection run_api_endpoint save_captured_request list_api_monitors list_api_proposals check_api_drift get_api_share_link share_api_endpoint share_api_collection list_api_runs

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-pipehero-pipehero/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-pipehero-pipehero)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.