Home / MCP registry index / io.usefulapi/estuary-flow
Estuary Flow MCP by usefulapi
io.usefulapi/estuary-flow in the official MCP registry.
Endpoint https://estuary-flow.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Inspect Estuary Flow captures, materializations, collections and stats.
We read its 15 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
estuary_list_catalog estuary_get_catalog_spec estuary_get_catalog_stats estuary_list_connectors estuary_list_connector_versions estuary_list_drafts estuary_list_draft_specs estuary_list_publications estuary_list_discovers estuary_list_roles estuary_get_tenant estuary_view_task_logs estuary_create_draft estuary_upsert_draft_spec estuary_publish_draft
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-estuary-flow)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.