Skip to content

Estuary Flow MCP by usefulapi

io.usefulapi/estuary-flowusefulapi.iostreamable-httpv1.40.4Scanned

Inspect Estuary Flow captures, materializations, collections and stats.

15 tools: 3 can delete or cancel things and 12 only read.

Tools: 3 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 1
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Estuary Flow MCP by usefulapi can do

The Estuary Flow MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (3 tools: estuary_create_draft, estuary_upsert_draft_spec and estuary_publish_draft). 12 tools only read.

2 tools read private data (estuary_get_catalog_stats and estuary_list_roles); 1 tool brings in text other people can write (estuary_list_connector_versions); 1 tool can send data out of your system (estuary_publish_draft). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 3Claude Code: deny
  • estuary_create_draftWRITE: create a new empty draft workspace (a staging area for catalog changes; does not affect live pipelines).No findings

    Why it is in this group

    • The name "estuary_create_draft" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: create a new empty draft workspace (a staging area for catalog changes; does not affect live pipelines). Estuary control-plane: POST /drafts. Returns the created row.

    Annotations the server declares

    • title: Create draft
    • destructiveHint: true
  • estuary_publish_draftWRITE (DESTRUCTIVE when dry_run=false): publish a draft.Can send data outNo findings

    Why it is in this group

    • The name "estuary_publish_draft" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "estuary_publish_draft" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    WRITE (DESTRUCTIVE when dry_run=false): publish a draft. dry_run=true (default) only VALIDATES the draft without changing anything. dry_run=false APPLIES the draft to the LIVE catalog — this can create, modify, or DELETE running data pipelines and their data. Set dry_run=false only when you intend to change live infrastructure. Estuary control-plane: POST /publications. Returns the publication row.

    Annotations the server declares

    • title: Publish draft
    • destructiveHint: true
  • estuary_upsert_draft_specWRITE: stage (insert or replace) a catalog spec inside a draft.No findings

    Why it is in this group

    • The name "estuary_upsert_draft_spec" says "upsert": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: stage (insert or replace) a catalog spec inside a draft. Edits only the draft — live pipelines are unaffected until the draft is published. Estuary control-plane: POST /draft_specs (upsert on draft_id,catalog_name). Returns the staged row.

    Annotations the server declares

    • title: Upsert draft spec
    • destructiveHint: true
Only reads 12Show 12 read-only tools
  • estuary_get_catalog_specGet one live catalog entity by its exact catalog_name, including the full serialized `spec` and compiled `built_spec`.No findings

    Why it is in this group

    • The name "estuary_get_catalog_spec" says "get": a word for reading.
    Description, as the server wrote it
    Get one live catalog entity by its exact catalog_name, including the full serialized `spec` and compiled `built_spec`. Estuary control-plane view live_specs_ext. PostgREST: GET /live_specs_ext?catalog_name=eq.<name>&limit=1.

    Annotations the server declares

    • title: Get catalog spec
    • readOnlyHint: true
  • estuary_get_catalog_statsGet usage/throughput stats for one catalog entity — bytes & docs read/written (both directions), usage_seconds, warnings/errors/failures, and txn_count — per time grain.Reads private dataNo findings

    Why it is in this group

    • The name "estuary_get_catalog_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "doc": it reads documents.
    Description, as the server wrote it
    Get usage/throughput stats for one catalog entity — bytes & docs read/written (both directions), usage_seconds, warnings/errors/failures, and txn_count — per time grain. Optionally bound by a timestamp range. Estuary control-plane view catalog_stats. PostgREST: GET /catalog_stats.

    Annotations the server declares

    • title: Get catalog stats
    • readOnlyHint: true
  • estuary_get_tenantGet the user's tenant(s) — quotas (tasks/collections), billing tiers, recurring charge, trial start, and payment provider.No findings

    Why it is in this group

    • The name "estuary_get_tenant" says "get": a word for reading.
    Description, as the server wrote it
    Get the user's tenant(s) — quotas (tasks/collections), billing tiers, recurring charge, trial start, and payment provider. Estuary control-plane table tenants. PostgREST: GET /tenants.

    Annotations the server declares

    • title: Get tenant
    • readOnlyHint: true
  • estuary_list_catalogList live catalog entities (captures, collections, materializations, tests) the user can read, with connector + last-publication metadata.No findings

    Why it is in this group

    • The name "estuary_list_catalog" says "list": a word for reading.
    Description, as the server wrote it
    List live catalog entities (captures, collections, materializations, tests) the user can read, with connector + last-publication metadata. Optionally filter by a catalog-name prefix and spec_type. Estuary control-plane view live_specs_ext. PostgREST: GET /live_specs_ext.

    Annotations the server declares

    • title: List catalog entities
    • readOnlyHint: true
  • estuary_list_connector_versionsList available versions (image tags) of connectors, with protocol and documentation URL.Reads text others writeNo findings

    Why it is in this group

    • The name "estuary_list_connector_versions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List available versions (image tags) of connectors, with protocol and documentation URL. Optionally filter by connector_id. Estuary control-plane table connector_tags. PostgREST: GET /connector_tags.

    Annotations the server declares

    • title: List connector versions
    • readOnlyHint: true
  • estuary_list_connectorsList the connector catalog — available capture/materialization Docker connectors, with titles, descriptions, and logos.No findings

    Why it is in this group

    • The name "estuary_list_connectors" says "list": a word for reading.
    Description, as the server wrote it
    List the connector catalog — available capture/materialization Docker connectors, with titles, descriptions, and logos. Optionally filter to recommended connectors. Estuary control-plane table connectors. PostgREST: GET /connectors.

    Annotations the server declares

    • title: List connectors
    • readOnlyHint: true
  • estuary_list_discoversList connector discovery jobs (auto-detecting bindings/resources for a capture).No findings

    Why it is in this group

    • The name "estuary_list_discovers" says "list": a word for reading.
    Description, as the server wrote it
    List connector discovery jobs (auto-detecting bindings/resources for a capture). Estuary control-plane table discovers. PostgREST: GET /discovers.

    Annotations the server declares

    • title: List discovers
    • readOnlyHint: true
  • estuary_list_draft_specsList the staged spec entries within a draft (each an insert/replace of a catalog entity pending publication).No findings

    Why it is in this group

    • The name "estuary_list_draft_specs" says "list": a word for reading.
    Description, as the server wrote it
    List the staged spec entries within a draft (each an insert/replace of a catalog entity pending publication). Estuary control-plane table draft_specs. PostgREST: GET /draft_specs.

    Annotations the server declares

    • title: List draft specs
    • readOnlyHint: true
  • estuary_list_draftsList the user's draft workspaces (staging areas for catalog edits before publishing).No findings

    Why it is in this group

    • The name "estuary_list_drafts" says "list": a word for reading.
    Description, as the server wrote it
    List the user's draft workspaces (staging areas for catalog edits before publishing). Estuary control-plane table drafts. PostgREST: GET /drafts.

    Annotations the server declares

    • title: List drafts
    • readOnlyHint: true
  • estuary_list_publicationsList publication history/status — each publish attempt of a draft; job_status carries the queued/success/failed outcome.No findings

    Why it is in this group

    • The name "estuary_list_publications" says "list": a word for reading.
    Description, as the server wrote it
    List publication history/status — each publish attempt of a draft; job_status carries the queued/success/failed outcome. Estuary control-plane table publications. PostgREST: GET /publications.

    Annotations the server declares

    • title: List publications
    • readOnlyHint: true
  • estuary_list_rolesList the roles/capabilities the current credential is granted — which catalog prefixes it can read/write/admin.Reads private data1 finding

    Why it is in this group

    • The name "estuary_list_roles" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "credential": it reads secrets.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "List the roles/capabilities the current credential is granted — which catalog prefixes it..."

      What this check looks for
    Description, as the server wrote it
    List the roles/capabilities the current credential is granted — which catalog prefixes it can read/write/admin. Read-only RPC. Estuary control-plane: POST /rpc/auth_roles.

    Annotations the server declares

    • title: List roles
    • readOnlyHint: true
  • estuary_view_task_logsFetch the log lines for a job by its logs_token (a UUID found on a publication, discover, or connector-tag record).No findings

    Why it is in this group

    • The name "estuary_view_task_logs" says "view": a word for reading.
    Description, as the server wrote it
    Fetch the log lines for a job by its logs_token (a UUID found on a publication, discover, or connector-tag record). Optionally page from a last-seen timestamp. Read-only RPC. Estuary control-plane: POST /rpc/view_logs.

    Annotations the server declares

    • title: View task logs
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__estuary-flow__estuary_publish_draft"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://estuary-flow.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://estuary-flow.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://estuary-flow.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://estuary-flow.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http estuary-flow https://estuary-flow.usefulapi.io/mcp
claude mcp add --transport http estuary-flow https://estuary-flow.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__estuary-flow__estuary_list_catalog",
      "mcp__estuary-flow__estuary_get_catalog_spec",
      "mcp__estuary-flow__estuary_get_catalog_stats",
      "mcp__estuary-flow__estuary_list_connectors",
      "mcp__estuary-flow__estuary_list_connector_versions",
      "mcp__estuary-flow__estuary_list_drafts",
      "mcp__estuary-flow__estuary_list_draft_specs",
      "mcp__estuary-flow__estuary_list_publications",
      "mcp__estuary-flow__estuary_list_discovers",
      "mcp__estuary-flow__estuary_list_roles",
      "mcp__estuary-flow__estuary_get_tenant",
      "mcp__estuary-flow__estuary_view_task_logs"
    ],
    "ask": [],
    "deny": [
      "mcp__estuary-flow__estuary_create_draft",
      "mcp__estuary-flow__estuary_upsert_draft_spec",
      "mcp__estuary-flow__estuary_publish_draft"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as estuary-flow. Review it before you use it.

Capability tags behind 4 rules
  • mcp__estuary-flow__estuary_get_catalog_stats private-data
  • mcp__estuary-flow__estuary_list_connector_versions untrusted-input
  • mcp__estuary-flow__estuary_list_roles private-data
  • mcp__estuary-flow__estuary_publish_draft outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/estuary-flow/verify?hash=855960a032f2be10cffe089bb9ac2e8d59a980f37ab594f08166ca5927bce3f4" | jq -e '.changed == false'

Pinned hash 855960a032f2, from Oct 25, 2026, 23:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/estuary-flow/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/estuary-flow
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/estuary-flow.svg)](https://radar.anlyon.com/servers/io.usefulapi/estuary-flow)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Estuary Flow MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Estuary Flow MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Estuary Flow MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: estuary_create_draft, estuary_upsert_draft_spec and estuary_publish_draft.

Can the Estuary Flow MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Estuary Flow MCP by usefulapi have?

15 tools: 3 destructive, 12 read. estuary_create_draft, estuary_upsert_draft_spec, estuary_publish_draft, estuary_list_catalog, estuary_get_catalog_spec, estuary_get_catalog_stats, estuary_list_connectors, estuary_list_connector_versions and 7 more.

Does the Estuary Flow MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Estuary Flow MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): estuary_publish_draft.

Has the Estuary Flow MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.