Smithery vs Pipedream MCP

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Pipedream MCP
   Smithery~partialprobed6/10

   llms.txt and docs.md are confirmed 404, so the specific llms.txt convention isn't supported, but Smithery does expose agent-oriented docs alternatives: docs served live over MCP (JSON-RPC initialize succeeds at /docs/mcp) and a machine-readable OpenAPI 3.1 spec at /docs/openapi.json that an agent could consume to understand the API. missing for 10: an actual llms.txt file, and any docs indicating agents are expected to consume these alternate machine-readable formats as a first-class 'llms.txt-style' workflow.

   • [probe] “PROBE llms.txt: HTTP 404 at https://smithery.ai/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://smithery.ai/docs.md”
   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed8/10

   A live probe confirms Pipedream serves markdown-formatted docs (mcp.md) that explicitly reference and point to a full llms.txt documentation index at pipedream.com/docs/llms.txt, directly matching the agent-oriented docs story. missing for 10: no independent confirmation that an agent actually consumed llms.txt successfully end-to-end (only that it is served/discoverable).

   • [probe] “PROBE docs-md: HTTP 200 at https://pipedream.com/docs/connect/mcp.md > ## Documentation Index > Fetch the complete documentation index at: h…”
   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Smithery
   Smithery✓fullprobed7/10

   Smithery ships a CLI (search/add/call tools) and a documented REST API with an OpenAPI 3.1 spec, service tokens scoped for AI agents/automation, and a live registry API queryable without interactive auth — all of which support scripted/headless use in CI pipelines. Runtime probes confirm the CLI installs and runs (`smithery --version`) and the API/registry endpoints respond programmatically. missing for 10: explicit CI/CD pipeline examples or GitHub Actions integration docs, and independent reports of real-world CI usage.

   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Service tokens let you safely expose Smithery to browsers, mobile apps, and AI agents without leaking your API key.”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”

   proof ↗⚑ flag

   Pipedream MCP~partialprobed6/10

   Pipedream MCP exposes a remote HTTP/SSE server and an SDK (@pipedream/sdk) that can be scripted programmatically, which supports headless/CI use, and the API is designed for developers to embed in their own apps/agents rather than requiring a GUI. However, the server requires a per-end-user binding (external user id) and OAuth-based account connection flows, which complicate fully unattended CI automation, and there is no explicit CI/headless-mode documentation or example. missing for 10: explicit CI/headless automation guide, evidence of non-interactive auth/token provisioning for unattended runs, and confirmation of stable long-running headless operation.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”
   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Smithery
   Smithery✓fullprobed8/10

   Smithery's core purpose is connecting/aggregating MCP servers: docs and probes confirm a REST/registry interface, hosted MCP endpoints with OAuth, deep links, uplink for local servers, and CLI/SDK tooling for adding and calling tools across connections, with runtime probes corroborating a live registry and per-server endpoints. Community reports of tool-description injection risks are a security caveat, not evidence the connection/tool-use mechanism fails. missing for 10: independent hands-on confirmation that an AI agent (not just probes) successfully invokes tools end-to-end across multiple aggregated servers, and resolution of the tool-description-injection security concerns.

   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [claimed-docs] “Deep links provide a seamless way to integrate Smithery MCPs into supported clients. When a user clicks a deep link from our server page, th…”
   • [claimed-docs] “Smithery handles OAuth, token refresh, and connection management automatically.”
   • [claimed-docs] “Connect to multiple servers and aggregate their tools”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Smithery✓fullprobed9/10

   Smithery is a hosting/registry platform (not itself an agent), so the exception applies and publishing an official MCP server endpoint is a fair, evidenced axis: docs describe OAuth-handled connections, deep linking, uplink, and typed SDKs, and independent probes confirm a live hosted MCP endpoint (server.smithery.ai/exa/mcp) requiring OAuth and even the docs site itself served over MCP (smithery.ai/docs/mcp) with a working CLI install. Missing for 10: no independent third-party report validating that connecting via the hosted server works end-to-end for an actual agent (only probe-level confirmation, not user testimonial), and community findings raise tool-description-injection risk that slightly tempers confidence though it doesn't contradict the connection mechanism itself.

   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [claimed-docs] “Deep links provide a seamless way to integrate Smithery MCPs into supported clients. When a user clicks a deep link from our server page, th…”
   • [claimed-docs] “Smithery handles OAuth, token refresh, and connection management automatically.”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed9/10

   Pipedream ships an official documented MCP server (remote.mcp.pipedream.net / mcp.pipedream.com) explicitly designed for agents/apps to connect and make tool calls across 3,000+ APIs, with SSE/streamable HTTP support, built-in auth, and an SDK — and a live probe confirms the endpoint is real and responds to JSON-RPC per the documented protocol. Missing for 10: an end-to-end probe showing a fully successful tool call (the live test only reached the 'external user id required' auth step, not actual tool invocation).

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “This is handled automatically by Pipedream’s MCP server and there’s no additional implementation required”
   • [claimed-docs] “The Pipedream MCP server supports both SSE and streamable HTTP transport types dynamically, with no configuration required by the developer …”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Smithery
   Smithery~partialprobed6/10

   There is concrete evidence of a working Smithery CLI (npm install @smithery/cli verified, version 4.11.1) with documented commands for searching the registry, adding MCP connections, finding/calling tools, and installing skills. However, the GitHub source is attributed to 'arcadeai-labs/smithery-cli' rather than an obviously first-party Smithery org, leaving some ambiguity about official first-party ownership, and there is no independent/community corroboration of CLI usage. Missing for 10: clearer first-party branding/ownership confirmation, official docs page dedicated to the CLI, and independent hands-on user reports.

   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [github] “Browse skills on the [Smithery Skills Registry](https://smithery.ai/skills) and install them with the upstream installer”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   Evidence covers Pipedream's MCP server, SDK (@pipedream/sdk), and chat app, but no mention of an official CLI tool for AI-native workflows. Missing for 10: any documentation or reference to a Pipedream CLI product.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Smithery✓fullprobed8/10

   Smithery exposes a real, documented public API: a registry API (registry.smithery.ai) queryable without keys, a full OpenAPI 3.1.0 spec (35 paths) confirmed live at smithery.ai/docs/openapi.json, and a REST/connection interface with OAuth and token scoping for programmatic/agent use, plus a CLI (smithery mcp/tool commands) for driving it. Initial llms.txt/docs.md probes 404'd but the actual OpenAPI spec and registry endpoints were independently verified live, satisfying 'documented public API' for an AI-native/agentic consumer. missing for 10: no independent third-party corroboration of API stability/versioning, and some docs endpoints (llms.txt) are absent despite the OpenAPI spec existing.

   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”
   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Service tokens let you safely expose Smithery to browsers, mobile apps, and AI agents without leaking your API key.”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed8/10

   Pipedream publishes detailed developer docs, an SDK (@pipedream/sdk), and a live MCP JSON-RPC endpoint (remote.mcp.pipedream.net) confirmed reachable and behaving per spec, giving AI-native developers a documented public API/protocol to drive tool calls programmatically. Missing for 10: independent third-party developer testimonials or case studies beyond vendor docs/probes.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Smithery
   Smithery✓fullclaimed7/10

   Smithery docs describe service tokens explicitly scoped to a specific app/connection/user metadata ('list and call tools on connections in my-app where metadata.userId is user-123 — nothing else'), plus encrypted write-only credential storage and namespace-scoped API keys, directly matching the least-privilege credential story for agents. Missing for 10: independent/hands-on verification that scope enforcement actually holds, and documentation of token revocation/expiry/audit controls.

   • [claimed-docs] “Service tokens let you safely expose Smithery to browsers, mobile apps, and AI agents without leaking your API key.”
   • [claimed-docs] “This token can list and call tools on connections in `my-app` where `metadata.userId` is `user-123` — nothing else.”
   • [claimed-docs] “Secure credential storage — Encrypted, write-only storage for API keys and tokens”
   • [claimed-docs] “Namespaces act as a shared workspace. Resources within a namespace can be managed by anyone with the appropriate API key scoped to that name…”

   proof ↗⚑ flag

   Pipedream MCP~partialprobed7/10

   Pipedream MCP issues per-end-user, revocable credentials via built-in OAuth-style account connections, and the live server enforces an external-user-id binding before serving tools, showing real per-user credential scoping rather than a single shared key. However, there is no explicit documentation of fine-grained scope selection (e.g., choosing specific read/write permissions per tool or API) that would constitute true least-privilege configuration. missing for 10: explicit least-privilege scope controls (choosing minimal permission sets per credential), independent/hands-on confirmation of revocation actually restricting access.

   • [claimed-docs] “Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization fl…”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Pipedream MCP
   Smithery✓fullprobed7/10

   Smithery auto-generates a typed TypeScript SDK for every published MCP server (smithery-docs-16), ships an official CLI (smithery-cli on GitHub) verified via live npm install (smithery-probe-rt-4), and exposes a documented OpenAPI 3.1 spec for platform API client generation, confirmed live via probe (smithery-probe-rt-3). This gives AI-native builders concrete, verified official SDK/CLI/API surfaces to build against. Missing for 10: SDKs beyond TypeScript (no Python/other language SDK evidence), and independent third-party corroboration of real-world SDK usage beyond Smithery's own docs/probes.

   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”
   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed8/10

   Pipedream documents and ships an official SDK (@pipedream/sdk) with a PipedreamClient class, integration guides for AI frameworks (mcpClient.tools()), and a runtime probe confirms the package installs and exports the client as documented. Missing for 10: coverage of SDKs in multiple languages beyond JS/TS and independent third-party corroboration of SDK usage in production apps.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”
   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Smithery
   Smithery~partialclaimed6/10

   Smithery's Triggers feature explicitly lets consumers subscribe to upstream events, proxying subscribe calls through to the server—directly matching webhook/event-subscription functionality for agentic use. However, this is documented only at a conceptual level with no depth on webhook delivery mechanics, retry/reliability guarantees, or independent hands-on verification. missing for 10: detailed webhook payload/delivery docs, independent corroboration of triggers working in practice, and coverage of failure/retry semantics.

   • [claimed-docs] “Triggers let an MCP server surface events from its upstream service. When a consumer activates a trigger via Smithery, Smithery proxies the …”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence pack describes Pipedream MCP purely as a tool-calling interface (auth, transport, tool listing) with no mention of webhook subscriptions or event-driven notifications delivered through MCP itself.

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Smithery
   Smithery~partialclaimed3/10

   Smithery's Triggers feature lets an MCP server surface upstream events which Smithery proxies to a consumer, hinting at event-driven automation, but there is no evidence of a scheduler, persistent background execution engine, or the platform itself running autonomous tasks — automation actually running requires an external agent that consumes the trigger. missing for 10: evidence of a scheduling/cron mechanism, autonomous execution loop hosted by Smithery, and confirmation that triggers fire without an active client agent.

   • [claimed-docs] “Triggers let an MCP server surface events from its upstream service. When a consumer activates a trigger via Smithery, Smithery proxies the …”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence describes Pipedream MCP as a tool-calling gateway that lets agents invoke APIs on behalf of users in real time, with no mention of scheduled, triggered, or persistently-running background automations. Missing for 10: any documentation of triggers, cron schedules, event-driven workflows, or autonomous execution outside an active agent session.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “This is handled automatically by Pipedream’s MCP server and there’s no additional implementation required”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to Pipedream MCP
   Smithery~partialprobed5/10

   Smithery's CLI exposes intent-based discovery ('smithery tool find [query] # Search tools by name or intent') and its docs are themselves served as an MCP endpoint that an agent can query conversationally, showing some natural-language-friendly interaction. However, the primary interface remains structured CLI subcommands (search, add, call) and REST/OpenAPI calls rather than a general natural-language command layer for operating the whole product. Missing for 10: a documented conversational/chat interface or explicit NL parsing across all product operations, and independent evidence of users successfully issuing free-form natural-language commands rather than structured queries.

   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”

   proof ↗⚑ flag

   Pipedream MCP~partialprobed6/10

   Pipedream MCP exposes tools via natural-language-capable chat interface (chat.pipedream.com) and MCP clients can invoke 3,000+ APIs through natural-language tool calls, with automatic tool loading and no manual auth flows needed. However, evidence is mostly first-party docs describing the underlying architecture rather than direct demonstration of natural-language command handling, and the live endpoint probe shows a per-user binding requirement that adds friction beyond pure NL commands. Missing for 10: independent/hands-on evidence of natural-language interaction quality, examples of actual NL prompts being translated to tool calls, and confirmation the chat app works smoothly without technical setup for end users.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “Try out Pipedream MCP in our chat app at chat.pipedream.com”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Smithery
   Smithery~partialprobed5/10

   Smithery exposes a full OpenAPI 3.1 spec (35 paths) and even serves its documentation itself as an MCP endpoint that agents can query interactively via JSON-RPC, which supports AI-native exploration of the API surface. However there's no evidence of a classic interactive reference UI (e.g., Swagger/Redoc 'try it out' runnable examples in-browser), and alternate machine-readable doc formats (llms.txt, docs.md) return 404s. missing for 10: an actual interactive/try-it-out API console with executable example requests, evidence of runnable code snippets in docs, independent confirmation of usability of the MCP-served docs.

   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://smithery.ai/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://smithery.ai/docs.md”

   proof ↗⚑ flag

   Pipedream MCP~partialclaimed3/10

   Pipedream provides docs with code snippets (docs-4, docs-5) and a live chat app (chat.pipedream.com) where users can try MCP tool calls interactively (docs-9), but there is no evidence of a dedicated interactive API reference/playground with runnable examples for the 3,000+ APIs. missing for 10: an actual interactive API explorer or sandboxed runnable code examples beyond a chat demo, independent confirmation of such a reference existing.

   • [claimed-docs] “Try out Pipedream MCP in our chat app at chat.pipedream.com”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “The Pipedream MCP server supports both SSE and streamable HTTP transport types dynamically, with no configuration required by the developer …”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Smithery
   Smithery✓fullprobed8/10

   A direct hands-on probe confirms a live, machine-readable OpenAPI 3.1.0 specification with 35 documented paths at smithery.ai/docs/openapi.json, which an agent could use to generate a client — squarely satisfying the story. Earlier probe attempts at guessed paths (openapi.json at root, swagger.json, etc.) 404'd, but the actual documented location succeeds. Missing for 10: first-party documentation explicitly announcing/linking the OpenAPI spec, and independent community confirmation of its use.

   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://smithery.ai/openapi.json, https://smithery.ai/swagger.json, https://smithery.ai/api/openapi.…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence describes Pipedream's MCP server, SDK, and docs (including an llms.txt index), but nowhere mentions a downloadable OpenAPI or equivalent machine-readable API spec for its endpoints/tools.

   ⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Pipedream MCP
   Smithery—none0/10

   Evidence shows Smithery's Uplink lets developers test an in-development MCP server against a real agent before publishing, but there is no mention of a distinct sandbox environment, test data isolation, or any mechanism preventing production data exposure during testing.

   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [claimed-docs] “You’re developing an MCP server and want to test it against a real agent before publishing.”

   proof ↗⚑ flag

   Pipedream MCP~partialclaimed3/10

   Docs mention getting started in a free 'development mode' for testing tool calls (docs-10), implying some separation from production usage, but there is no explicit documentation of a sandbox environment, test data isolation, or guarantees that dev-mode calls don't touch real production accounts/data. Missing for 10: explicit sandbox/test-vs-prod environment docs, confirmation that test accounts are isolated from real user data, and independent verification of this isolation.

   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Smithery—none0/10

   Evidence shows Smithery has an OpenAPI 3.1.0 spec and a documented REST/MCP interface, but nothing in the docs or probes describes API versioning conventions or a deprecation policy for breaking changes.

   ⚑ flag

   Pipedream MCP—none0/10

   The evidence pack covers MCP tool usage, authentication, and transport, but contains no mention of API versioning scheme, version numbers, or a documented deprecation policy for the MCP server or SDK. missing for 10: any documented API version scheme, changelog, deprecation notice process, or backward-compatibility guarantees.

   ⚑ flag

Multi tenant

1. platform-engineerMaintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials

   weight 3 · round to Pipedream MCP
   Smithery~partialcommunity6/10

   Smithery's token-scoping docs show scoped tokens tied to per-user metadata (e.g. a token limited to connections where metadata.userId is 'user-123'), and secure credential storage/automatic refresh are documented, which directly supports per-end-user credential isolation for a platform-engineer building on top of Smithery. However, there's no first-party documentation of a full per-user account management workflow (provisioning, revocation, auditing across many end users) beyond the single scoping example, and independent security research flagged real vulnerabilities (tool description injection, path traversal) that raise doubts about credential-boundary robustness in practice. missing for 10: dedicated multi-tenant/per-end-user account management docs beyond one scoping example, evidence of token revocation/rotation workflows at scale, and independent verification that scoped tokens hold up against the reported security findings.

   • [claimed-docs] “Service tokens let you safely expose Smithery to browsers, mobile apps, and AI agents without leaking your API key.”
   • [claimed-docs] “This token can list and call tools on connections in `my-app` where `metadata.userId` is `user-123` — nothing else.”
   • [claimed-docs] “Automatic token refresh — Credentials stay valid without manual intervention”
   • [claimed-docs] “Secure credential storage — Encrypted, write-only storage for API keys and tokens”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”
   • [community] “Security researchers detailed a path traversal vulnerability in Smithery's MCP server hosting that could be escalated into a supply chain at…”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed8/10

   Docs describe per-end-user connected accounts with built-in auth/token storage/refresh handled by Pipedream, external_user_id scoping so agents act only on that user's credentials, and user-facing revocation of connected accounts; the live probe confirms the MCP server enforces an external user id binding before serving tools, corroborating the scoping claim. missing for 10: independent multi-tenant audit or case study showing token isolation at scale, and detail on scoped token permission granularity beyond per-account connection.

   • [claimed-docs] “Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization fl…”
   • [claimed-docs] “This is handled automatically by Pipedream’s MCP server and there’s no additional implementation required”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”
   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Oauth

1. developerLet the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh

   weight 3 · round to Pipedream MCP
   Smithery✓fullprobed7/10

   Docs explicitly describe Smithery handling OAuth flows, encrypted write-only credential storage, and automatic token refresh (smithery-docs-1,2,3,13), and this is corroborated by a live probe showing an OAuth challenge gating a hosted MCP endpoint (smithery-probe-rt-2). missing for 10: no independent hands-on confirmation of encryption-at-rest implementation details or token refresh behavior over time, and community evidence focuses on unrelated security findings rather than corroborating credential vaulting.

   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Automatic token refresh — Credentials stay valid without manual intervention”
   • [claimed-docs] “Secure credential storage — Encrypted, write-only storage for API keys and tokens”
   • [claimed-docs] “Smithery handles OAuth, token refresh, and connection management automatically.”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed8/10

   Docs explicitly state Pipedream Connect/MCP handles OAuth/user authentication, token storage, and refresh automatically with no additional implementation required, and this is corroborated by a live probe showing the remote MCP endpoint enforcing per-user auth binding. Revocable access confirms credential lifecycle management beyond just initial OAuth. Missing for 10: explicit documentation of encryption-at-rest/vaulting mechanics for stored credentials and independent third-party verification of refresh behavior over time.

   • [claimed-docs] “Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization fl…”
   • [claimed-docs] “This is handled automatically by Pipedream’s MCP server and there’s no additional implementation required”
   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

White label

1. platform-engineerWhite-label the authorization flow with my own branding and my own OAuth app credentials

   weight 1 · round drawn
   Smithery—none0/10

   The evidence pack describes Smithery's own OAuth/credential-management infrastructure (managed auth, token scoping, secure storage) but contains no mention of white-labeling the auth flow with custom branding or bringing your own OAuth app/client credentials to replace Smithery's identity — no BYO-OAuth-app, custom domain, or branding customization feature is documented anywhere.

   ⚑ flag

   Pipedream MCP—none0/10

   The evidence describes Pipedream's built-in authentication handling and revocable user connections, but nothing in the pack mentions white-labeling the OAuth flow with custom branding or letting platform engineers substitute their own OAuth app credentials. This is a fair axis for a connect/auth platform, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization fl…”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Smithery—none0/10

   Evidence shows Smithery lets an agent connect to and aggregate tools from multiple servers, and its registry API can be queried/paginated for many entries, but there is no documented batch/bulk operation capability (e.g., bulk tool calls, mass server management, batch CRUD) that would let a user perform bulk actions across many items at once. missing for 10: batch tool-call API, bulk server management commands, mass connection/config updates, any documented multi-item transaction support.

   ⚑ flag

   Pipedream MCP—none0/10

   The evidence describes Pipedream MCP exposing thousands of individual API tools and handling auth/transport automatically, but nothing in the pack documents a bulk/batch operation capability (e.g., applying one action across many items or records in a single call). Missing for 10: any documentation of batch/bulk tool calls, looping over item sets, or multi-item transaction support.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “Slack: Send messages, manage channels, create reminders, and more”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Smithery
   Smithery~partialclaimed3/10

   Smithery's 'Triggers' feature lets an MCP server surface upstream events and lets a consumer 'activate' a trigger, which is a thin form of event-driven automation, but there's no evidence of a user-facing rule-definition mechanism (e.g., 'if event X then run action Y') or a rules engine — it only proxies subscribe calls. Missing for 10: a documented rule/condition-action authoring interface, examples of automated action execution on trigger events, and independent confirmation the feature works end-to-end.

   • [claimed-docs] “Triggers let an MCP server surface events from its upstream service. When a consumer activates a trigger via Smithery, Smithery proxies the …”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence pack describes Pipedream MCP purely as a tool-calling/connector layer (auth, transport, tool listing) for agents to invoke APIs on demand — it contains no mention of defining rules, event triggers, or automatic actions firing on events. Missing for 10: any documentation of trigger/rule definitions, event-based workflow automation, or scheduled/conditional execution within the MCP server itself.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Smithery—none0/10

   Smithery's docs describe on-demand tool connections, OAuth/credential management, and event-driven 'Triggers' that proxy subscribe calls from upstream services, but nothing describes cron-like recurring job scheduling or workflow automation on a timer. Triggers are reactive (event-based), not scheduled/recurring, so the specific capability asked for is unevidenced.

   • [claimed-docs] “Triggers let an MCP server surface events from its upstream service. When a consumer activates a trigger via Smithery, Smithery proxies the …”
   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [claimed-docs] “If you’ve already deployed an MCP server elsewhere, you can publish it directly on Smithery via the URL method.”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence pack describes Pipedream MCP purely as a tool-calling gateway (auth, tool discovery, transport) for invoking 3,000+ APIs on demand, with no mention of scheduling, cron triggers, or recurring workflow execution via MCP.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Smithery—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Pipedream MCP—none0/10

   Evidence covers tool access, auth, and transport for Pipedream MCP, but nothing addresses versioning of automations, review workflows, or rollback capability. No mention of change history, diffing, approval flows, or reverting to prior configurations.

   ⚑ flag

Bridge

1. developerBridge a locally running MCP server into the platform as a managed remote connection without deploying it

   weight 1 · round to Smithery
   Smithery✓fullclaimed8/10

   Smithery's Uplink feature explicitly exposes an MCP server running on any local machine as a regular Smithery connection, letting developers test/use a locally running server against real agents without deploying it, and this is backed by scoped tokens and managed OAuth/credential handling. missing for 10: independent/hands-on confirmation of Uplink working end-to-end (only first-party docs cited) and no detail on latency/reliability of the bridged local connection.

   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [claimed-docs] “You’re developing an MCP server and want to test it against a real agent before publishing.”
   • [claimed-docs] “You want to run a private tool for yourself or your team without hosting it.”
   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Service tokens let you safely expose Smithery to browsers, mobile apps, and AI agents without leaking your API key.”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   All evidence describes Pipedream operating its own hosted remote MCP server (exposing 3,000+ APIs/tools) that clients connect to — not a mechanism for a developer to take a locally-running custom MCP server and have Pipedream bridge/host it remotely without deployment. No evidence pack item mentions importing, registering, or proxying an external/local MCP server through Pipedream's platform.

   ⚑ flag

Access control

1. platform-engineerRestrict which servers and individual tools an agent may call through allowlists or per-tool access control

   weight 2 · round to Smithery
   Smithery~partialclaimed6/10

   Smithery's token-scoping feature lets platform engineers issue tokens restricted to specific connections/namespaces (e.g., 'list and call tools on connections in my-app where metadata.userId is user-123 — nothing else'), which functions as a coarse allowlist mechanism, and namespaces further scope API-key access to a workspace. However, the evidence shows scoping is at the connection/namespace level, not explicit per-tool allow/deny lists within a single server. Missing for 10: documented fine-grained per-tool allow/deny configuration, independent/hands-on verification that tool-level restrictions are enforced, and any admin UI or policy examples showing individual tool blocking within an allowed connection.

   • [claimed-docs] “Service tokens let you safely expose Smithery to browsers, mobile apps, and AI agents without leaking your API key.”
   • [claimed-docs] “This token can list and call tools on connections in `my-app` where `metadata.userId` is `user-123` — nothing else.”
   • [claimed-docs] “Namespaces act as a shared workspace. Resources within a namespace can be managed by anyone with the appropriate API key scoped to that name…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence describes authentication, revocable account access, and automatic tool loading, but nowhere documents allowlisting of specific MCP servers or granular per-tool access control for platform engineers. The docs even state tools are 'automatically loaded' rather than filtered, and no admin/allowlist configuration is described. missing for 10: allowlist configuration UI/API, per-tool enable/disable controls, evidence of restricting which servers an agent may reach.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Audit

1. platform-engineerSee a log of every tool call that passed through the platform, with enough detail to audit or replay what an agent did

   weight 2 · round drawn
   Smithery—none0/10

   No evidence describes any audit logging, tool-call history, or replay capability for platform engineers—docs cover connection, credential management, publishing, tokens, and namespaces but never mention logs of tool calls passing through the gateway.

   ⚑ flag

   Pipedream MCP—none0/10

   No evidence describes any logging, audit trail, or replay capability for tool calls made through Pipedream MCP; documentation covers auth, transport, and connectivity but is silent on observability/audit logs. Missing for 10: any mention of a tool-call log, audit trail UI/API, replay mechanism, or retention/detail guarantees for platform engineers.

   ⚑ flag

Catalog

1. developerReach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform

   weight 3 · round to Pipedream MCP
   Smithery✓fullprobed8/10

   Smithery is a registry/marketplace connecting to a large catalog of third-party MCP servers (Exa, Context7, Browserbase, Google Sheets, Brave Search, etc.), with a live registry API confirmed via probe returning searchable server entries with useCount/verified metadata, plus hosted per-server MCP endpoints (server.smithery.ai) and CLI search/add tooling. Community evidence confirms real scale (100+ servers scanned) though also raises security concerns about tool description injection, which affects trust/quality but not the breadth-of-catalog claim itself. Missing for 10: independently verified total count of hundreds/thousands of listings and first-party data on catalog size/growth.

   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Exa - Search the live web, access LinkedIn profiles, do deep research, and more”
   • [claimed-docs] “Context7 - Reference the latest docs for most major SDKs and frameworks directly in Cursor or Claude Code”
   • [claimed-docs] “Browserbase - Control a remote web browser using Stagehand”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed9/10

   Docs and live probe confirm Pipedream MCP exposes 3,000+ APIs and 10,000+ tools with built-in auth, and the remote MCP endpoint is live and functioning (requiring per-user binding as documented). Missing for 10: independent third-party verification of the full catalog size beyond vendor docs.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization fl…”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”

   proof ↗⚑ flag

Connect

1. developerPoint my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure

   weight 3 · round to Pipedream MCP
   Smithery✓fullprobed8/10

   Docs and live probes confirm Smithery hosts remote MCP server endpoints (server.smithery.ai/<server>/mcp) that clients can point at directly, with OAuth/token handling, deep links, and typed SDKs generated automatically — no server deployment needed by the developer. Independent probe evidence (smithery-probe-rt-2) shows the hosted endpoint is live and gated by managed OAuth rather than requiring self-hosting infrastructure. missing for 10: independent hands-on developer accounts (outside security research) confirming a smooth end-to-end connect experience beyond documentation and infra probes.

   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”
   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [claimed-docs] “If you’ve already deployed an MCP server elsewhere, you can publish it directly on Smithery via the URL method.”
   • [claimed-docs] “Smithery handles OAuth, token refresh, and connection management automatically.”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”

   proof ↗⚑ flag

   Pipedream MCP✓fullprobed9/10

   Pipedream documents a hosted remote MCP endpoint (mcp.pipedream.com / remote.mcp.pipedream.net) that clients can point at without deploying infrastructure, with SSE/streamable HTTP transport auto-negotiated and tool loading handled server-side. A live probe confirms the endpoint is reachable and responds per the JSON-RPC protocol (requiring only a per-end-user binding parameter, not extra infra). Missing for 10: independent third-party (non-vendor) confirmation of a full end-to-end tool call succeeding beyond the initialize handshake.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “The Pipedream MCP server supports both SSE and streamable HTTP transport types dynamically, with no configuration required by the developer …”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [claimed-docs] “Try out Pipedream MCP in our chat app at chat.pipedream.com”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “official MCP server documented at https://pipedream.com/docs/connect/mcp”

   proof ↗⚑ flag

Generate

1. developerTurn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing

   weight 2 · round to Smithery
   Smithery~partialclaimed4/10

   Smithery's docs show a hosting/publishing path for MCP servers already built in code (URL method, MCPB bundles, server-card metadata) which removes protocol plumbing for deployment, but there is no evidence of an OpenAPI-spec ingestion or auto-generation feature that turns an existing REST API definition into an MCP server — the publish flow assumes you already have MCP-shaped code or a deployed server. Missing for 10: OpenAPI-to-MCP conversion tooling, any first-party or independent proof of generating a server from an OpenAPI spec, and confirmation that 'custom code' can be arbitrary non-MCP code rather than code already written against the MCP SDK.

   • [claimed-docs] “If you’ve already deployed an MCP server elsewhere, you can publish it directly on Smithery via the URL method.”
   • [claimed-docs] “For local stdio servers — Smithery distributes a pre-built MCPB bundle that clients download and run locally.”
   • [claimed-docs] “If automatic scanning can’t complete (auth wall, required configuration, or other issues), you can provide server metadata manually via a st…”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   All evidence describes consuming Pipedream's existing hosted MCP server (mcp.pipedream.com / remote.mcp.pipedream.net) to call Pipedream's pre-built 3,000+ API integrations on behalf of end users — none of it shows a developer importing their own OpenAPI spec or custom code to generate a new hosted MCP server without protocol plumbing. Missing for 10: any documentation of OpenAPI import, custom-code-to-MCP conversion, or a 'create your own MCP server' workflow.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “Pipedream Connect includes built-in user authentication for more than APIs via MCP, which means you don’t need to build any authorization fl…”
   • [claimed-docs] “This is handled automatically by Pipedream’s MCP server and there’s no additional implementation required”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Publish

1. developerPublish my own MCP server on the platform for distribution, discovery, and installation by others

   weight 2 · round to Smithery
   Smithery✓fullprobed8/10

   Docs clearly describe multiple publishing paths (URL method for already-deployed servers, MCPB bundle distribution for local stdio servers, automatic scanning or manual server-card metadata) resulting in a registry listing with generated TypeScript SDK, and the registry API probe confirms servers are discoverable/searchable by others without auth. Security researchers did find vulnerabilities/prompt-injection risks in some published servers, but this reflects on registry quality, not on whether publishing/discovery/installation works. missing for 10: independent hands-on account of a developer successfully publishing a server end-to-end, and clearer detail on install flow verification post-publish.

   • [claimed-docs] “If you’ve already deployed an MCP server elsewhere, you can publish it directly on Smithery via the URL method.”
   • [claimed-docs] “For local stdio servers — Smithery distributes a pre-built MCPB bundle that clients download and run locally.”
   • [claimed-docs] “If automatic scanning can’t complete (auth wall, required configuration, or other issues), you can provide server metadata manually via a st…”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   All evidence describes Pipedream's own hosted MCP server (remote.mcp.pipedream.net) that exposes Pipedream's 3,000+ pre-built API integrations to developers' apps/agents — it does not show any mechanism for a third-party developer to publish their own custom MCP server on the platform for other users to discover and install. Missing for 10: any publishing/registry workflow, discovery/marketplace listing feature, or installation flow for user-authored MCP servers.

   ⚑ flag

Triggers

1. developerSubscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them

   weight 2 · round to Smithery
   Smithery✓fullclaimed7/10

   Smithery documents a Triggers feature that explicitly lets consumers subscribe to event streams surfaced from an upstream service, with Smithery proxying the subscribe call to the server instead of requiring polling. This directly matches the story of subscribing an agent to downstream app events via webhooks/triggers rather than polling. Missing for 10: independent/hands-on confirmation that triggers work reliably in production, and more detail on delivery guarantees or webhook payload handling.

   • [claimed-docs] “Triggers let an MCP server surface events from its upstream service. When a consumer activates a trigger via Smithery, Smithery proxies the …”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The evidence pack only describes Pipedream MCP as a tool-calling interface (action/tool invocation via JSON-RPC, authentication, transport details) — nothing shows agents subscribing to webhook/trigger events pushed from downstream apps via MCP; this is a request/response tool model, not an event-subscription model.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Analytics

1. platform-engineerSee usage analytics for the servers and tools my org consumes or publishes — call volumes, users, errors, and cost

   weight 2 · round drawn
   Smithery—none0/10

   The evidence pack documents connection, publishing, token scoping, triggers, and SDK generation, but nothing about a dashboard or API for org-level usage analytics (call volumes, per-user breakdowns, error rates, cost). The only quantitative signal found is a per-server 'useCount' field in the public registry listing, which is not org-scoped consumption/error/cost analytics.

   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   Evidence covers MCP connectivity, auth, transport, and tool loading, but nothing addresses usage analytics dashboards for call volumes, user counts, error rates, or cost tracking across servers/tools an org consumes or publishes.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Smithery
   Smithery~partialprobed7/10

   Smithery exposes a documented, live OpenAPI 3.1 spec (35 paths) and a keyless registry API, plus a CLI (`smithery mcp add`, `smithery tool call`) that mirrors core UI actions like discovering, connecting, and invoking MCP servers — showing broad API/CLI parity with the UI for the main workflows (search, connect, publish via URL, call tools). However, no evidence explicitly confirms that secondary UI-only features (team/namespace management, trigger configuration, token scoping setup) are fully API-reachable, and llms.txt/docs.md convenience endpoints 404. missing for 10: explicit confirmation that admin/team features (namespaces, triggers, token scoping) are configurable via the API/CLI rather than only the UI, and independent hands-on verification beyond the vendor's own OpenAPI spec.

   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”
   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [claimed-docs] “If you’ve already deployed an MCP server elsewhere, you can publish it directly on Smithery via the URL method.”
   • [claimed-docs] “Namespaces act as a shared workspace. Resources within a namespace can be managed by anyone with the appropriate API key scoped to that name…”
   • [claimed-docs] “Triggers let an MCP server surface events from its upstream service. When a consumer activates a trigger via Smithery, Smithery proxies the …”

   proof ↗⚑ flag

   Pipedream MCP~partialprobed5/10

   Pipedream MCP exposes tool-calling and account-connection via API/MCP server (remote.mcp.pipedream.net, SDK), and end users can connect/revoke accounts via mcp.pipedream.com, but the evidence pack does not show that all UI-driven configuration (e.g., building/publishing custom workflows, managing app settings, full admin/dashboard functionality) is exposed through the API/MCP interface. missing for 10: evidence that non-tool-calling UI features (workflow building, org/team admin, billing, dashboard analytics) are also accessible via API/MCP, and independent confirmation beyond vendor docs.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Smithery—none0/10

   No evidence anywhere in the pack of a data-export feature, account data portability, or open-format export for users leaving the platform; documentation covers connections, tokens, and MCP server publishing but nothing about exporting stored user data (connections, credentials metadata, namespaces) in an open format.

   ⚑ flag

   Pipedream MCP—none0/10

   Pipedream MCP is a connectivity/integration layer for tool calls to third-party APIs; the evidence covers authentication, tool loading, and revocable access, but nothing addresses exporting a user's own data from Pipedream in open formats or account/data portability for leaving the platform.

   ⚑ flag

3. ai-native userSelf-host the core product

   weight 3 · round drawn
   Smithery—none0/10

   Evidence describes Smithery only as a hosted registry/platform (registry.smithery.ai, server.smithery.ai) with OAuth-gated hosted MCP endpoints; 'Uplink' lets users expose their own local MCP server as a connection into the hosted Smithery service, but this is not self-hosting the Smithery platform itself. No docs, GitHub repo, or probes indicate a self-hostable/open-source deployment of the core product.

   • [claimed-docs] “Uplink exposes an MCP server running on any machine as a regular Smithery connection.”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://server.smithery.ai/exa/mcp returned HTTP 401 with an OAuth challenge — the hoste…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   All evidence describes Pipedream MCP as a hosted service (mcp.pipedream.com, remote.mcp.pipedream.net) with no mention of a self-hosted or open-source deployment option for the core MCP server; the SDK/npm package is a client library, not a self-hostable server.

   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”

   proof ↗⚑ flag

Pricing

1. developerPrototype my agent's tool connections on a meaningful free tier before paying anything

   weight 1 · round to Pipedream MCP
   Smithery—none0/10

   The evidence pack contains extensive documentation on Smithery's features, registry, and integrations but no mention of pricing tiers, a free tier, usage limits, or billing at all — the axis is applicable to a hosted MCP platform but simply unevidenced.

   ⚑ flag

   Pipedream MCP~partialprobed5/10

   Docs explicitly state developers can 'get started for free in development mode' and try the hosted chat app, and the SDK/server are confirmed live and installable without payment friction. However, there's no detail on what limits/quotas define the free tier (rate limits, tool-call caps, upgrade triggers), so it's unclear how 'meaningful' the free tier is for real prototyping at scale. Missing for 10: specific free-tier quotas/limits, comparison to paid tiers, and independent developer accounts confirming the free tier suffices for non-trivial prototyping.

   • [claimed-docs] “To use Pipedream MCP in your own app or agent to make tool calls on behalf of your users, you can get started for free in development mode”
   • [claimed-docs] “Try out Pipedream MCP in our chat app at chat.pipedream.com”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”

   proof ↗⚑ flag

2. developerSee transparent pricing per tool call or connection plus documented rate limits before committing to the platform

   weight 2 · round drawn
   Smithery—none0/10

   No evidence pack item mentions pricing tiers, per-call costs, or documented rate limits anywhere in Smithery's docs, GitHub, or probes; the documentation covers connection, tokens, and hosting but is silent on pricing/rate limits, and repeated probes (llms.txt, docs.md, openapi) surface no pricing/rate-limit schema.

   ⚑ flag

   Pipedream MCP—none0/10

   Evidence only covers MCP setup, auth, and transport mechanics; no citation discloses per-tool-call pricing, connection pricing tiers, or documented rate limits. A passing mention of 'free in development mode' does not constitute transparent pricing or rate-limit documentation.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Smithery—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or geographic storage controls; Smithery's docs cover credential storage, token scoping, and connection management but not where data is physically stored.

   ⚑ flag

   Pipedream MCP—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or compliance controls for where data is stored; the docs focus on tool access, authentication, and transport mechanics.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Smithery—none0/10

   No evidence in the pack addresses AI training data usage, opt-out controls, or any data-privacy policy regarding model training; docs focus on credential storage, OAuth, and connection routing, not training-data opt-out.

   ⚑ flag

   Pipedream MCP—none0/10

   The evidence pack covers MCP connectivity, authentication, and revocable account access, but contains no mention of AI-training data usage policies or opt-out controls for Pipedream MCP.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Pipedream MCP
   Smithery—none0/10

   The evidence pack covers credential storage encryption and token scoping but contains no mention of data retention policies, user-initiated data deletion, or account/data export controls. This is a fair privacy-posture question for a platform managing credentials and connections, so the absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

   Pipedream MCP~partialclaimed4/10

   Docs confirm users can revoke connected-account access at any time, which covers a piece of deletion control, but there is no documented policy on data retention periods, deletion of stored request/response logs, or export/erasure guarantees. missing for 10: explicit data retention timelines, log/data deletion mechanisms beyond account revocation, compliance/GDPR-style deletion guarantees.

   • [claimed-docs] “Revocable access: Users can revoke access to their connected accounts at any time”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Smithery—none0/10

   No evidence anywhere in the pack mentions a telemetry/usage-tracking opt-out setting, privacy policy toggle, or data-collection disclosure for Smithery; the docs cover credential security and OAuth but never address analytics/telemetry opt-out.

   ⚑ flag

   Pipedream MCP—none0/10

   No evidence anywhere in the pack addresses telemetry, analytics, or usage-tracking opt-out settings for Pipedream MCP; docs cover authentication, transport, and account revocation but not telemetry controls.

   ⚑ flag

Api

1. ai agentQuery the platform's registry or catalog through a documented API to discover servers and tools programmatically

   weight 3 · round to Smithery
   Smithery✓fullprobed9/10

   A live probe confirms an agent can query https://registry.smithery.ai/servers keylessly and get a machine-readable JSON catalog (displayName, qualifiedName, verified, etc.), and a documented OpenAPI 3.1 spec with 35 paths is served at smithery.ai/docs/openapi.json, enabling programmatic client generation. This is corroborated by the smithery-cli's 'mcp search'/'tool find' commands for registry/tool discovery. Missing for 10: no independent third-party report of an agent successfully building a full client purely from the OpenAPI spec, and llms.txt/docs.md convenience endpoints 404.

   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [probe] “PROBE openapi (2026-09-05): GET https://smithery.ai/docs/openapi.json returned HTTP 200 with an OpenAPI 3.1.0 description (35 documented pat…”
   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”

   proof ↗⚑ flag

   Pipedream MCP~partialprobed5/10

   Pipedream documents a programmatic `mcpClient.tools()` call that 'automatically loads all available tools' for a connected app, and the live endpoint probe confirms the MCP server responds to JSON-RPC requests, showing some machine-readable tool discovery. However, there is no documented registry/catalog API for browsing the full list of 3,000+ integrated apps/servers before connecting — discovery is scoped per-user/per-app rather than a global catalog query. Missing for 10: a documented catalog/registry-listing endpoint (not just per-connection tools()), independent confirmation of full catalog enumeration.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Metadata

1. developerInspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it

   weight 2 · round to Smithery
   Smithery~partialprobed6/10

   The registry API (probe-rt-1) exposes machine-readable metadata per server — displayName, qualifiedName, isDeployed, remote, verified — covering hosting/transport attributes, and community security audits (comm-1, comm-2) confirm that tool description fields are visible and inspectable pre-connection (that's how injected instructions were found). The CLI's `tool find` command (gh-2) and per-server typed SDKs generated from tool schemas (docs-16) further support schema visibility, but there is no single documented endpoint or UI view that surfaces full input schemas plus transport plus hosting attributes together in one inspection step. Missing for 10: a documented unified 'server detail' API/UI showing input schemas explicitly, and independent confirmation that transport type (stdio/http/websocket) is surfaced pre-connect.

   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”
   • [community] “Real examples pulled from Smithery-hosted servers: Context7, Google Sheets, Senzia, and Brave Search tool descriptions contained agent-direc…”

   proof ↗⚑ flag

   Pipedream MCP~partialclaimed4/10

   Docs show that tools can be listed/loaded via mcpClient.tools() and that transport (SSE/streamable HTTP) is documented, giving partial visibility into a server's capabilities before use, but there is no evidence of a registry listing with explicit input schemas or hosting attributes for inspection prior to connecting. missing for 10: schema inspection UI/API, hosting attribute metadata, and a registry-style browsing view for listed servers before connection.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “The Pipedream MCP server supports both SSE and streamable HTTP transport types dynamically, with no configuration required by the developer …”
   • [claimed-docs] “Slack: Send messages, manage channels, create reminders, and more”

   proof ↗⚑ flag

Playground

1. developerExercise an MCP server's tools from a browser-based inspector or playground before integrating it

   weight 2 · round to Pipedream MCP
   Smithery—none0/10

   The evidence pack documents Smithery's registry, REST connect flow, OAuth/token handling, uplink, deep links, and CLI tool-calling, but nothing describes a browser-based inspector or playground UI for interactively testing a server's tools before integration. Since a registry/marketplace product could plausibly ship such a try-before-integrate UI, the axis applies, but no evidence confirms it exists.

   ⚑ flag

   Pipedream MCP~partialprobed6/10

   Pipedream explicitly offers a browser-based 'chat app' at chat.pipedream.com for trying out its MCP tools before integrating, and mcp.pipedream.com lets users connect/authorize accounts, which functions as a lightweight playground. However, there's no dedicated 'MCP inspector' UI shown, no independent hands-on report confirming the chat app's tool-exercising experience, and the live endpoint requires per-user binding before serving tools. Missing for 10: independent/hands-on verification of the chat playground's tool-calling UX, and a dedicated inspector-style tool browser beyond the chat interface.

   • [claimed-docs] “Try out Pipedream MCP in our chat app at chat.pipedream.com”
   • [claimed-docs] “As an end user: Connect your accounts through Pipedream MCP at mcp.pipedream.com”
   • [probe] “PROBE mcp-endpoint (2026-09-05): POST initialize to https://remote.mcp.pipedream.net answered a JSON-RPC error over HTTP 400 ({"jsonrpc":"2.…”

   proof ↗⚑ flag

Search

1. developerSearch and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent

   weight 3 · round to Smithery
   Smithery✓fullprobed8/10

   Smithery ships both a CLI (`smithery mcp search`, `smithery tool find [query]`) and a keyless registry REST API (registry.smithery.ai/servers) that returns a machine-readable catalog with names, descriptions, verification status and usage counts, letting developers search/browse servers and tools by capability before connecting; docs also list example servers (Exa, Context7, Browserbase) illustrating capability-based discovery. Missing for 10: no evidence of a rich web UI faceted-browse/filter-by-category experience or independent hands-on review of the discovery UX itself beyond the CLI/API probes.

   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [claimed-docs] “Exa - Search the live web, access LinkedIn profiles, do deep research, and more”
   • [claimed-docs] “Context7 - Reference the latest docs for most major SDKs and frameworks directly in Cursor or Claude Code”
   • [claimed-docs] “Browserbase - Control a remote web browser using Stagehand”

   proof ↗⚑ flag

   Pipedream MCP~partialclaimed4/10

   Pipedream advertises a large catalog (3,000+ APIs, 10,000+ tools) and lists example apps like Slack with their supported actions, implying some browsable catalog exists, but there is no direct evidence of a search/browse UI or capability-based filtering mechanism for developers to explore before integration. missing for 10: explicit search/filter interface, capability-tagging or query API, independent confirmation of browsing experience.

   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [claimed-docs] “Slack: Send messages, manage channels, create reminders, and more”
   • [claimed-docs] “Try out Pipedream MCP in our chat app at chat.pipedream.com”

   proof ↗⚑ flag

Cli

1. developerDrive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agents

   weight 2 · round to Smithery
   Smithery~partialprobed6/10

   Smithery ships an official CLI (@smithery/cli, confirmed installable via npm and version-checked) with commands to search/add/call MCP servers, and docs cover publishing servers (URL method, MCPB bundles, server-card metadata) plus auth via OAuth/service tokens and installing into agents via deep links/uplink. However, evidence does not clearly show a unified CLI-driven build-and-push workflow (e.g., 'smithery build' or 'smithery deploy' subcommands) — the CLI evidence only shows search/add/call, while publish/build steps are documented as web/manual flows rather than CLI-driven. missing for 10: CLI subcommands for authenticate/build/push in one flow, independent hands-on confirmation of end-to-end publish-via-CLI, and clarity on whether install-into-agents is CLI-native vs deep-link/manual.

   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [github] “Browse skills on the [Smithery Skills Registry](https://smithery.ai/skills) and install them with the upstream installer”
   • [claimed-docs] “If you’ve already deployed an MCP server elsewhere, you can publish it directly on Smithery via the URL method.”
   • [claimed-docs] “For local stdio servers — Smithery distributes a pre-built MCPB bundle that clients download and run locally.”
   • [claimed-docs] “If automatic scanning can’t complete (auth wall, required configuration, or other issues), you can provide server metadata manually via a st…”
   • [claimed-docs] “Deep links provide a seamless way to integrate Smithery MCPs into supported clients. When a user clicks a deep link from our server page, th…”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/smithery/): a JSON-RPC initialize POST to https://smithery.ai/docs/mc…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Frameworks

1. developerPlug the platform's tools into major agent frameworks and SDKs (Vercel AI SDK, LangChain, CrewAI, OpenAI or Anthropic SDKs) with documented adapters

   weight 2 · round drawn
   Smithery~partialclaimed5/10

   Smithery documents a dedicated Vercel AI SDK integration with automatic OAuth/token handling and multi-server tool aggregation (docs-13/14), and every published server gets an auto-generated typed SDK (docs-16), but the evidence pack shows no documented adapters for LangChain, CrewAI, or OpenAI/Anthropic SDKs specifically. Missing for 10: documented LangChain adapter, documented CrewAI adapter, documented OpenAI/Anthropic SDK adapter, and independent/hands-on confirmation beyond first-party docs.

   • [claimed-docs] “Smithery handles OAuth, token refresh, and connection management automatically.”
   • [claimed-docs] “Connect to multiple servers and aggregate their tools”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”
   • [claimed-docs] “Smithery gives you a simple REST interface for connecting to MCP servers. Instead of implementing the MCP protocol directly, handling OAuth …”

   proof ↗⚑ flag

   Pipedream MCP~partialprobed5/10

   Pipedream documents a generic MCP client integration page (docs/connect/mcp/ai-frameworks) showing a code snippet (mcpClient.tools()) for loading tools automatically, implying framework-agnostic SDK integration, and ships an official @pipedream/sdk package confirmed via runtime probe. However, the evidence pack never names or shows adapters for specific major frameworks like Vercel AI SDK, LangChain, CrewAI, or OpenAI/Anthropic SDKs explicitly — only a generic MCP client pattern is shown. Missing for 10: explicit documented code samples/adapters per named framework (LangChain, CrewAI, Vercel AI SDK, OpenAI/Anthropic SDKs), independent hands-on confirmation of each integration working.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”
   • [probe] “PROBE runtime (recorded 2026-09-04, see data/mcp-infrastructure/proofs/pipedream-mcp/): `npm install @pipedream/sdk` completed into a throwa…”

   proof ↗⚑ flag

Security

1. platform-engineerRely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them

   weight 2 · round to Smithery
   Smithery!disputedcontradicted4/10

   Smithery's docs mention 'automatic scanning' of published servers (smithery-docs-11), implying some vetting pipeline, but independent research directly contradicts its effectiveness: scanning the top 100 registry servers found 22 with security findings (4 critical) including tool-description prompt-injection attacks embedded in widely-used servers like Context7 and Brave Search that execute silently on agent connection (smithery-comm-1, smithery-comm-2), and researchers separately found a path-traversal vulnerability in Smithery's own hosting escalatable to a supply-chain attack (smithery-comm-3). Missing for 10: any documented remediation/removal process for flagged malicious servers, transparency on scan methodology or coverage, and evidence the automatic scanning actually catches behavioral/prompt-injection risks rather than just metadata issues.

   • [claimed-docs] “If automatic scanning can’t complete (auth wall, required configuration, or other issues), you can provide server metadata manually via a st…”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”
   • [community] “Real examples pulled from Smithery-hosted servers: Context7, Google Sheets, Senzia, and Brave Search tool descriptions contained agent-direc…”
   • [community] “Security researchers detailed a path traversal vulnerability in Smithery's MCP server hosting that could be escalated into a supply chain at…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   Evidence covers authentication, transport, tool loading, and revocable access, but nothing in the pack describes any scanning, vetting, or security review process for listed servers/tools before agents use them.

   ⚑ flag

Signals

1. developerCompare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges

   weight 2 · round to Smithery
   Smithery~partialprobed6/10

   The registry API (probe evidence) exposes useCount and verified fields per server, plus isDeployed/remote status, giving developers concrete usage and verification signals to compare servers; docs also mention automatic scanning during publish which implies some quality vetting. However, there is no documented explicit 'quality score' metric or dedicated health/liveness-check endpoint beyond isDeployed, and independent security scans found unflagged risky servers in the top 100, showing the published signals don't capture all quality concerns. Missing for 10: an explicit scoring/quality-score field, a dedicated liveness/health-check mechanism, and corroboration that verification badges reliably reflect security vetting.

   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [claimed-docs] “If automatic scanning can’t complete (auth wall, required configuration, or other issues), you can provide server metadata manually via a st…”
   • [community] “Scanned the top 100 servers on Smithery's registry; 22 of 100 flagged at least one security finding (28 total, 4 critical, 24 high), most co…”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   Evidence only covers Pipedream MCP's functionality (auth, transport, tool listing) but contains no usage counts, health/liveness checks, quality scores, or verification badges for comparing servers.

   ⚑ flag

Tool search

1. ai agentSearch and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context

   weight 2 · round to Smithery
   Smithery✓fullprobed7/10

   Smithery's CLI exposes explicit meta-tools — `mcp search`, `tool find [query]`, and `tool call <connection> <tool>` — letting an agent discover and invoke tools by intent at runtime rather than preloading every tool definition, and the registry API is confirmed live and keylessly searchable in a probe returning a machine-readable catalog. missing for 10: no evidence the search/find/call meta-tools are themselves exposed as callable MCP tools inside a live agent session (vs. CLI-level usage), and no independent benchmark showing reduced context footprint from this pattern.

   • [github] “smithery mcp search [term] # Search the Smithery registry smithery mcp add <url> # Add an MCP server connectio…”
   • [github] “smithery tool find [query] # Search tools by name or intent smithery tool call <connection> <tool> [args] # Call a tool”
   • [probe] “PROBE registry-api (2026-09-05): GET https://registry.smithery.ai/servers?pageSize=3 with NO API key returned HTTP 200 with a machine-readab…”
   • [claimed-docs] “Every MCP server published on Smithery gets a typed TypeScript SDK generated from its tool and trigger schemas.”

   proof ↗⚑ flag

   Pipedream MCP—none0/10

   Pipedream MCP's own docs describe `mcpClient.tools()` as automatically loading *all* available tools rather than exposing meta-tools (e.g., search_tools/load_tool) for on-demand discovery, and no evidence pack item mentions a meta-tool/dynamic-search pattern for reducing context load.

   • [claimed-docs] “tools: await mcpClient.tools(), // Automatically loads all available tools”
   • [claimed-docs] “Add Pipedream MCP to your app or agent to make tool calls on behalf of your users to 3,000+ APIs and 10,000+ tools.”

   proof ↗⚑ flag