Rank #2 of 6 in MCP Infrastructure & Registries
Showcase


Try itExperimental
See what an agent can do with Smithery before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s -X POST https://smithery.ai/docs/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Auth credentials — stories about auth credentials in this arenaAuth credentialsevidence →
Stories about auth credentials in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Deployment self host — stories about deployment self host in this arenaDeployment self hostevidence →
Stories about deployment self host in this arena
Gateway controls — stories about gateway controls in this arenaGateway controlsevidence →
Stories about gateway controls in this arena
Hosted servers — stories about hosted servers in this arenaHosted serversevidence →
Stories about hosted servers in this arena
Observability analytics — stories about observability analytics in this arenaObservability analyticsevidence →
Stories about observability analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Registry discovery — stories about registry discovery in this arenaRegistry discoveryevidence →
Stories about registry discovery in this arena
Sdk clients — stories about sdk clients in this arenaSdk clientsevidence →
Stories about sdk clients in this arena
Tool curation quality — stories about tool curation quality in this arenaTool curation qualityevidence →
Stories about tool curation quality in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Smithery stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Versioning policy · API sandbox · Full data export
Subscribe to events via webhooks
~6/10
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
✓7/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓8/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
—0/10
Explore an interactive API reference with runnable examples
~5/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
~6/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
~5/10
Plug MCP servers into this product so it can use their tools
✓8/10
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~3/10
Auth credentials — stories about auth credentials in this arenaAuth credentials
Stories about auth credentials in this arena
Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials
~6/10
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh
✓7/10
White-label the authorization flow with my own branding and my own OAuth app credentials
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Deployment self host — stories about deployment self host in this arenaDeployment self host
Stories about deployment self host in this arena
Gateway controls — stories about gateway controls in this arenaGateway controls
Stories about gateway controls in this arena
Hosted servers — stories about hosted servers in this arenaHosted servers
Stories about hosted servers in this arena
Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
✓8/10
Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
✓8/10
Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing
~4/10
Publish my own MCP server on the platform for distribution, discovery, and installation by others
✓8/10
Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them
✓7/10
Observability analytics — stories about observability analytics in this arenaObservability analytics
Stories about observability analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Registry discovery — stories about registry discovery in this arenaRegistry discovery
Stories about registry discovery in this arena
Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
✓9/10
Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
~6/10
Exercise an MCP server's tools from a browser-based inspector or playground before integrating it
—–
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
✓8/10
Sdk clients — stories about sdk clients in this arenaSdk clients
Stories about sdk clients in this arena
Tool curation quality — stories about tool curation quality in this arenaTool curation quality
Stories about tool curation quality in this arena
Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
!4/10
Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
~6/10
Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context
✓7/10
Sorted by importance (agentic first) (high → low) · 52/52 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed⚿ | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed⚿ | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed⚿ | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full± | 7/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial± | 6/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none± | 0/10 | ||
Query the platform's registry or catalog through a documented API to discover servers and tools programmatically C Api | ai agent | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 3 | full | 9/10 | Tprobed | |
Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure C Connect | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 3 | full | 8/10 | Tprobed⚿ | |
Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform C Catalog | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 3 | full | 8/10 | Tprobed⚿ | |
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent C Search | developer | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 3 | full | 8/10 | Tprobed | |
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh C Oauth | developer | Auth credentials — stories about auth credentials in this arenaAuth credentials | 3 | full | 7/10 | Tprobed⚿ | |
Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials C Multi tenant | platform-engineer | Auth credentials — stories about auth credentials in this arenaAuth credentials | 3 | partial | 6/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 3/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ⚿ | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Publish my own MCP server on the platform for distribution, discovery, and installation by others C Publish | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 2 | full | 8/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 7/10 | Tprobed⚿ | |
Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context C Tool search | ai agent | Tool curation quality — stories about tool curation quality in this arenaTool curation quality | 2 | full | 7/10 | Tprobed | |
Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them C Triggers | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 2 | full | 7/10 | Cclaimed | |
Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges C Signals | developer | Tool curation quality — stories about tool curation quality in this arenaTool curation quality | 2 | partial | 6/10 | Tprobed | |
Drive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agents C Cli | developer | Sdk clients — stories about sdk clients in this arenaSdk clients | 2 | partial | 6/10 | Tprobed | |
Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it C Metadata | developer | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 2 | partial | 6/10 | Tprobed | |
Restrict which servers and individual tools an agent may call through allowlists or per-tool access control C Access control | platform-engineer | Gateway controls — stories about gateway controls in this arenaGateway controls | 2 | partial | 6/10 | Cclaimed | |
Plug the platform's tools into major agent frameworks and SDKs (Vercel AI SDK, LangChain, CrewAI, OpenAI or Anthropic SDKs) with documented adapters C Frameworks | developer | Sdk clients — stories about sdk clients in this arenaSdk clients | 2 | partial | 5/10 | Cclaimed | |
Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them C Security | platform-engineer | Tool curation quality — stories about tool curation quality in this arenaTool curation quality | 2 | disputed | 4/10 | Dcontradicted | |
Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing C Generate | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 2 | partial | 4/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
See usage analytics for the servers and tools my org consumes or publishes — call volumes, users, errors, and cost C Analytics | platform-engineer | Observability analytics — stories about observability analytics in this arenaObservability analytics | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Exercise an MCP server's tools from a browser-based inspector or playground before integrating it C Playground | developer | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
See a log of every tool call that passed through the platform, with enough detail to audit or replay what an agent did C Audit | platform-engineer | Gateway controls — stories about gateway controls in this arenaGateway controls | 2 | none | untested | none yet | |
See transparent pricing per tool call or connection plus documented rate limits before committing to the platform G Pricing | developer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | none | untested | none yet | |
Bridge a locally running MCP server into the platform as a managed remote connection without deploying it C Bridge | developer | Deployment self host — stories about deployment self host in this arenaDeployment self host | 1 | full | 8/10 | Cclaimed | |
Prototype my agent's tool connections on a meaningful free tier before paying anything G Pricing | developer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet | |
White-label the authorization flow with my own branding and my own OAuth app credentials C White label | platform-engineer | Auth credentials — stories about auth credentials in this arenaAuth credentials | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 33 stories with headroom
What would move Smithery’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
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.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
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.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
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.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
partialq3/10moves PA Scoreimpact 21
Missing: a documented rule/condition-action authoring interface, examples of automated action execution on trigger events, and independent confirmation the feature works end-to-end.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
partialq3/10moves Built-in AIimpact 21
Missing: evidence of a scheduling/cron mechanism, autonomous execution loop hosted by Smithery, and confirmation that triggers fire without an active client agent.
Automation depth — how much of the product can run unattendedPerform bulk operations across many items at once
nonemoves PA Scoreimpact 20
Missing: batch tool-call API, bulk server management commands, mass connection/config updates, any documented multi-item transaction support.
Automation depth — how much of the product can run unattendedSchedule recurring jobs or workflows
nonemoves PA Scoreimpact 20
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.
Showing the top 8 of 33 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 32 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs32 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Plug MCP servers into this product so it can use their tools
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials
- Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh
- Define rules that trigger actions automatically on events
- Bridge a locally running MCP server into the platform as a managed remote connection without deploying it
- Restrict which servers and individual tools an agent may call through allowlists or per-tool access control
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
- Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing
- Publish my own MCP server on the platform for distribution, discovery, and installation by others
- Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them
- Do everything through the API that I can do in the UI
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
- Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
- Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
- Drive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agents
- Plug the platform's tools into major agent frameworks and SDKs (Vercel AI SDK, LangChain, CrewAI, OpenAI or Anthropic SDKs) with documented adapters
- Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
- Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
- Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context
GitHub README13 stories
- Run the product headlessly / in CI for automation
- Plug MCP servers into this product so it can use their tools
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Operate the product with natural-language commands
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Do everything through the API that I can do in the UI
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
- Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
- Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
- Drive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agents
- Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context
Servers docs12 stories
- Run the product headlessly / in CI for automation
- Plug MCP servers into this product so it can use their tools
- Drive the product through a documented public API
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
- Publish my own MCP server on the platform for distribution, discovery, and installation by others
- Do everything through the API that I can do in the UI
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
- Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
- Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
- Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
- Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context
Exa docs7 stories
- Plug MCP servers into this product so it can use their tools
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
- Do everything through the API that I can do in the UI
Hacker News7 stories
- Plug MCP servers into this product so it can use their tools
- Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Publish my own MCP server on the platform for distribution, discovery, and installation by others
- Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
- Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
- Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
llms.txt2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s -X POST https://smithery.ai/docs/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -s -X POST https://smithery.ai/docs/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
event: message
data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"resources":{"listChanged":true}},"serverInfo":{"name":"Smithery Documentation","version":"1.0.0"},"instructions":"This Model Context Protocol server provides search and retrieval tools for the Smithery Documentation site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the r
$curl -si -X POST https://server.smithery.ai/exa/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://server.smithery.ai/exa/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401
date: Sat, 05 Sep 2026 00:27:13 GMT
content-type: application/json
content-length: 76
access-control-allow-origin: *
www-authenticate: Bearer error="invalid_[redacted]", error_description="Missing Authorization header", resource_metadata="https://server.smithery.ai/.well-known/oauth-protected-resource/exa/mcp"
cf-placement: remote-YYZ
access-control-expose-headers: mcp-session-id,www-authenticate
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=HyuoSfsH%2B29owMBgfCXeR%2B9k%2BBZUSpV%2Bxpih47tEInXv%2BjW4yN2gnExj2Dcb0wV8AH82OIuJHTef5m6jwvqjZlolmmDgcE8Y%2BTBlEr1zdYC8yFQZTnkCcnk69SlPfC45xQVU5rY%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
server: cloudflare
cf-ray: a3611b61aeb1545f-SJC
alt-svc: h3=":443"; ma=86400
{"error":"invalid_[redacted]","error_description":"Missing Authorization header"}
$mktemp -d && npm install @smithery/cli && ./node_modules/.bin/smithery --versionreproduced$ mktemp -d && npm install @smithery/cli && ./node_modules/.bin/smithery --version \ added 2 packages in 308ms \4.11.1
$curl -s 'https://registry.smithery.ai/servers?pageSize=3&q=browser' | head -c 900reproduced$ curl -s 'https://registry.smithery.ai/servers?pageSize=3&q=browser' | head -c 900
{"servers":[{"id":"1a19dc2d-039e-4016-8410-b1181ede14af","qualifiedName":"browserbase","namespace":"browserbase","slug":"","displayName":"Browserbase","description":"Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to interact with web pages, take screenshots, and run parallel sessions in a cloud browser environment.","iconUrl":"https://www.google.com/s2/favicons?domain=www.browserbase.com&sz=64","verified":true,"useCount":433,"remote":true,"isDeployed":true,"unlisted":false,"inactive":false,"createdAt":"2024-12-13T15:47:00.443Z","homepage":"https://www.browserbase.com/","bySmithery":false,"owner":"org_01KNB3CMNPNA0PSSGJ1M0FTZDG","score":0.042703150912106136},{"id":"5690e101-ecdd-46ec-ab3c-9da3806ef33c","qualifiedName":"apify","namespace":"apify","slug":"","displayName":"Apify","description":"Web scraping and automation platform. Run scrapers,
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
11 of 15 testable claims verified · 1 contradicted → integrity 60/100
20 distinct capability claims found in Smithery’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
11
Verified
3
Unverified
1
Contradicted
17
Undersold
Verified (16)
“Provides a REST interface to MCP servers, handling protocol, OAuth and credential management for you”
Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructurefullproof ↗
“Provides a REST interface to MCP servers, handling protocol, OAuth and credential management for you”
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refreshfullproof ↗
“Automatically refreshes OAuth tokens so credentials stay valid without manual work”
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refreshfullproof ↗
“Stores API keys and tokens in encrypted, write-only credential storage”
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refreshfullproof ↗
“Scoped tokens can be restricted to only list/call tools for a specific end-user's connections”
Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentialspartialproof ↗
“Servers already deployed elsewhere can be published on Smithery via a simple URL registration method”
Publish my own MCP server on the platform for distribution, discovery, and installation by othersfullproof ↗
“Local stdio servers are distributed as a pre-built MCPB bundle that clients download and run locally”
Publish my own MCP server on the platform for distribution, discovery, and installation by othersfullproof ↗
“Servers that can't be auto-scanned can supply metadata manually via a static server-card.json file”
Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to itpartialproof ↗
“Aggregates connections to multiple MCP servers so an agent can use all their tools together”
Plug MCP servers into this product so it can use their toolsfullproof ↗
“Generates a typed TypeScript SDK automatically from each published server's tool and trigger schemas”
“Official CLI can search the registry and add MCP server connections”
“Official CLI can search the registry and add MCP server connections”
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agentfullproof ↗
“Official CLI can search for tools by name/intent and call a tool on a connection”
“Official CLI can search for tools by name/intent and call a tool on a connection”
Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my contextfullproof ↗
“Provides a Skills Registry where users can browse and install skills via an upstream installer”
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agentfullproof ↗
“Catalog includes deep third-party integrations like Exa, Context7 and Browserbase for web search, docs and browser control”
Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platformfullproof ↗
Unverified (4)
“Uplink bridges a locally running MCP server into a managed remote Smithery connection without deploying it”
Bridge a locally running MCP server into the platform as a managed remote connection without deploying itfullproof ↗
“Service tokens let you expose Smithery safely to browsers, mobile apps and AI agents without leaking the main API key”
Issue scoped/least-privilege API credentials for an agentfullproof ↗
“Triggers let a server surface upstream events, with Smithery proxying subscribe calls through to the server”
Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling themfullproof ↗
“Supports running a private tool for yourself or your team without needing to host it separately”
Bridge a locally running MCP server into the platform as a managed remote connection without deploying itfullproof ↗
Contradicted (1)
“Lets developers test an in-progress MCP server against a real agent before publishing it”
Exercise an MCP server's tools from a browser-based inspector or playground before integrating itnone
Undersold (17)
Point an agent at llms.txt or agent-oriented docspartialproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Restrict which servers and individual tools an agent may call through allowlists or per-tool access controlpartialproof ↗
Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbingpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Query the platform's registry or catalog through a documented API to discover servers and tools programmaticallyfullproof ↗
Drive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agentspartialproof ↗
Plug the platform's tools into major agent frameworks and SDKs (Vercel AI SDK, LangChain, CrewAI, OpenAI or Anthropic SDKs) with documented adapterspartialproof ↗
Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badgespartialproof ↗
Claims outside our story set (2)
Real capability claims found in Smithery’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Deep links let supported clients auto-configure an MCP connection when a user clicks the link”
source ↗“Namespaces act as shared workspaces so a team can manage resources under one scoped API key”
source ↗
Business model
MCP registry with hosted connections: browsing and publishing to the registry is free; managed connections and hosted tool calls are metered on paid plans. Operated by Arcade.dev since the 2026 acquisition.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP 100% (30d, checked every 6h since Sep 8 '26)
