MCP servers observed by Lowdown

io.github.pipehero/pipehero MCP server: daily status and tool changes

Answered initialize and tools/list on all 21 daily checks recorded in the last 30 days (2026-10-06 to 2026-10-26); 25 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; tool definitions last changed on 2026-10-08 after 1 days without change; no agent-reported interactions.

Does it respond?

Latest daily check: 2026-10-26: the server answered initialize and tools/list.

• Observed days in the last 30: 21
• Answered initialize and tools/list: 21
• Required authentication: 0
• No response: 0
• Remotes differed: 0

Does it require authentication?

It did not return HTTP 401/403 on any of the 21 observed days. Lowdown checks without credentials.

Did its tools change recently?

Tool definitions changed on 2 of 20 compared days.

• 2026-10-08: input or output schemas changed, descriptions changed, server version changed; tool count 24 → 25
• 2026-10-07: input or output schemas changed, descriptions changed, server version changed; tool count 22 → 24

What tools does it list?

25 tools on 2026-10-26:

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

MCP Registry declaration

• Registry name: io.github.pipehero/pipehero
• Declared version: 0.1.0
• Status: active
• Declared hosts: mcp.pipehero.app