01 · Records and state owned
MCP server listings, namespaces, deployments, connections, OAuth/token configuration, sessions, server configuration, and usage analytics.
Smithery
Smithery
A prominent MCP connection and registry platform that manages server discovery, OAuth, credentials, sessions, and client connectivity—useful as infrastructure but distinct from the BYO-UI editorial layer.
Interface hosts, builders & integration infrastructureInterface host and orchestration layerAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Discover, connect to, configure, and observe remote or local MCP servers through Smithery’s distribution and connection tooling.
03 · Actions and write paths
Invoke connected server tools; the actual writes are defined by each server rather than Smithery itself.
04 · Authentication and permissions
Smithery sessions, OAuth/token handling, server configuration, and downstream server authentication apply.
05 · Monitoring, approval, and recovery
Verify publisher and server trust, minimize connected tools, isolate credentials, and treat third-party server code as part of the security boundary.
06 · Gaps and implementation limits
Smithery is registry/connection infrastructure, not evidence that every listed server is first-party, secure, or production ready.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
MCP integration infrastructure; upstream capabilities varySmithery registry, gateway and managed MCP connection platformCurrent production service
Role: infrastructure
Read scope: Publish and distribute remote or local MCP servers, connect to them through REST or CLI, manage OAuth, tokens, sessions and configuration, and collect server analytics and usage signals
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access2
UI extensibility4
Portability4
Observability4
Documentation2
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Smithery ships these experiences.
Single-platform patterns
- MCP connection and credential-control plane
- BYO-UI application shell
- Capability gateway
- Agent and tool operations console
Multi-platform compositions
- Smithery + systems of record: byo-ui application shell
- Smithery + systems of production + systems of engagement: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
2 recorded sources
DocumentationRepresentative source
https://smithery.ai/docs ↗Official Smithery documentation describes infrastructure for discovering, publishing and connecting MCP servers, not one governed business-data provider. Verification establishes publisher claims, while server quality,…
- Publisher updated
- May 22, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party infrastructure review
HomepageSource inventory
https://smithery.ai/ ↗Registry and platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.