io.usefulapi/estuary-flow
REMOTE · ESTUARY-FLOW.USEFULAPI.IO · SCANNED OCT 4
Inspect Estuary Flow captures, materializations, collections and stats.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1443 tokens (~96/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/estuary-flow MCP server?
io.usefulapi/estuary-flow is a hosted endpoint at https://estuary-flow.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · estuary-flow.usefulapi.io
claude mcp add --transport http io-usefulapi-estuary-flow 'https://estuary-flow.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-estuary-flow": {
"url": "https://estuary-flow.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-estuary-flow": {
"type": "http",
"url": "https://estuary-flow.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-estuary-flow] url = "https://estuary-flow.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-estuary-flow": {
"type": "remote",
"url": "https://estuary-flow.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-estuary-flow --url 'https://estuary-flow.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-estuary-flow:
url: "https://estuary-flow.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-estuary-flow": {
"Transport": "http",
"Url": "https://estuary-flow.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-estuary-flow -t streamable-http -u 'https://estuary-flow.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-estuary-flow": {
"type": "http",
"url": "https://estuary-flow.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +45
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 3 Oct 26 −44
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 2 Oct 26 +44
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 30 Sept 26 +10
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://estuary-flow.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of estuary-flow.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://estuary-flow.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://estuary-flow.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://estuary-flow.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://estuary-flow.usefulapi.io/mcp |
| Authorisation server | https://estuary-flow.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://estuary-flow.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://estuary-flow.usefulapi.io/mcp | HTTPS enforced | 301 | https://estuary-flow.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estuary_create_draft Create draft ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Optional human-readable note describing the draft's purpose. |
No output schema declared.
No examples provided.
estuary_get_catalog_spec Get catalog spec ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_name | string | yes | The exact catalog name (e.g. acmeCo/inventory/products). |
No output schema declared.
No examples provided.
estuary_get_catalog_stats Get catalog stats ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_name | string | yes | The exact catalog name to report stats for. |
| grain | string | – | Time grain of each stats row (default daily). |
| limit | integer | – | Max rows to return (PostgREST limit). |
| ts_end | string | – | Filter: stats at/before this ISO 8601 timestamp (ts lte). |
| ts_start | string | – | Filter: stats at/after this ISO 8601 timestamp (ts gte). |
No output schema declared.
No examples provided.
estuary_get_tenant Get tenant ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows to return (PostgREST limit). |
No output schema declared.
No examples provided.
estuary_list_catalog List catalog entities ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows to return (PostgREST limit). |
| name_prefix | string | – | Filter to catalog names starting with this prefix (PostgREST like.<prefix>* wildcard). |
| offset | integer | – | Row offset for paging (PostgREST offset). |
| spec_type | string | – | Filter by entity type. |
No output schema declared.
No examples provided.
estuary_list_connector_versions List connector versions ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_id | string | – | Filter by connector id (from estuary_list_connectors). |
| limit | integer | – | Max rows to return (PostgREST limit). |
No output schema declared.
No examples provided.
estuary_list_connectors List connectors ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows to return (PostgREST limit). |
| recommended | boolean | – | Filter to recommended (true) / non-recommended (false) connectors. |
No output schema declared.
No examples provided.
estuary_list_discovers List discovers ~58
List connector discovery jobs (auto-detecting bindings/resources for a capture). Estuary control-plane table discovers. PostgREST: GET /discovers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows to return (PostgREST limit). |
No output schema declared.
No examples provided.
estuary_list_draft_specs List draft specs ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | yes | The draft id to list staged specs for. |
| limit | integer | – | Max rows to return (PostgREST limit). |
No output schema declared.
No examples provided.
estuary_list_drafts List drafts ~59
List the user's draft workspaces (staging areas for catalog edits before publishing). Estuary control-plane table drafts. PostgREST: GET /drafts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows to return (PostgREST limit). |
No output schema declared.
No examples provided.
estuary_list_publications List publications ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows to return (PostgREST limit). |
No output schema declared.
No examples provided.
estuary_list_roles List roles ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| min_capability | string | – | Only return grants at/above this capability (default x_00 = all). |
No output schema declared.
No examples provided.
estuary_publish_draft Publish draft ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Optional human-readable note for this publication. |
| draft_id | string | yes | The draft id to publish. |
| dry_run | boolean | – | If true (DEFAULT), only validate without applying. Set false to APPLY to the live catalog. |
No output schema declared.
No examples provided.
estuary_upsert_draft_spec Upsert draft spec ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_name | string | yes | The catalog name of the entity being staged (e.g. acmeCo/inventory/products). |
| draft_id | string | yes | The draft id to stage the spec into. |
| spec | object | yes | The catalog spec JSON object (passed through verbatim). |
| spec_type | string | yes | The entity type of the staged spec. |
No output schema declared.
No examples provided.
estuary_view_task_logs View task logs ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bearer_token | string | yes | The logs_token (UUID) from a publications/discovers/connector_tags row. |
| last_logged_at | string | – | ISO 8601 timestamp — return log lines after this point (2-arg view_logs overload). |
No output schema declared.
No examples provided.
What is the io.usefulapi/estuary-flow MCP server?
io.usefulapi/estuary-flow is an MCP server listed in the public MCP registry as io.usefulapi/estuary-flow. Inspect Estuary Flow captures, materializations, collections and stats. This page covers its hosted endpoint (https://estuary-flow.usefulapi.io/mcp).
Is the io.usefulapi/estuary-flow MCP server safe to use?
io.usefulapi/estuary-flow scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/estuary-flow MCP server expose?
io.usefulapi/estuary-flow exposes 15 tools: estuary_list_catalog, estuary_get_catalog_spec, estuary_get_catalog_stats, estuary_list_connectors, estuary_list_connector_versions, and 10 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.
Does the io.usefulapi/estuary-flow MCP server require authentication?
Yes. io.usefulapi/estuary-flow asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/estuary-flow MCP server still maintained?
io.usefulapi/estuary-flow is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.