Home / MCP registry index / com.pipefork/management
Pipefork Management MCP
com.pipefork/management in the official MCP registry.
Endpoint https://www.pipefork.com/mcp.
The registry describes it as: Manage Pipefork API projects, drafts, connections, secrets, and deployments through MCP.
We read its 27 tools on 2026-10-22. 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.
Tools it advertises
api_list api_get api_create draft_get draft_validate endpoint_create endpoint_update endpoint_delete step_create step_update step_delete step_reorder secret_list secret_create secret_rotate secret_deactivate connection_list connection_get connection_create connection_update deployment_list deployment_get_state deployment_deploy deployment_promote deployment_rollback deployment_undeploy deployment_history
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-pipefork-management)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.