Publisher note
Smithery should be framed as both discovery and operational infrastructure for MCP. It combines registry search and publishing with connection APIs, OAuth/session handling, scoped service tokens, analytics, gateway behavior, and deployment types.
What Smithery does
Smithery is not just a list of MCP servers. The source pack supports a broader frame: discovery, publishing, distribution, analytics, gateway behavior, hosted or external deployment types, local stdio support, and connection APIs for clients that need to attach to MCP servers.
Registry and discovery signals
Smithery registry search exposes signals such as verified, remote, isDeployed, useCount, homepage, owner, namespace, and score. These are useful filters for shortlisting, but they should not be rewritten as universal guarantees. Not every Smithery listing is hosted, remote, deployed, or verified.
Connection and credential model
The strongest Smithery differentiator is operational: docs describe OAuth flows, credentials, sessions, automatic token refresh, API keys, and scoped service tokens. For browser, mobile, and agent contexts, the safer default is scoped service tokens rather than exposing broad API keys to untrusted clients or autonomous agents.
Deployment types
Smithery docs include hosted_shttp, external_shttp, and stdio deployment types. That matters for procurement because local stdio, external remote HTTP, and hosted/gateway patterns all move the trust boundary. The page should explicitly separate search/discovery claims from deployment and gateway claims.
Publishing and scanning
Smithery publishing docs say it scans servers for metadata such as tools, prompts, and resources, and that auth-required servers may require authentication to complete scanning. This is useful for catalog quality, but it is not the same as a full code audit or production readiness review.
Who should evaluate Smithery
Smithery is a strong fit for teams that need to discover MCP servers and also manage how agents connect to them. It is especially relevant when OAuth, sessions, token refresh, analytics, or deployment modes are part of the decision.
Related topics
- Smithery MCP
- MCP registry
- MCP gateway
- MCP deployment
- Smithery