Arcade.dev has acquired Smithery, the prominent public registry and hosting platform that emerged as the fastest route for developers to discover and deploy Model Context Protocol (MCP) servers. The acquisition, announced on August 5, includes the integration of Smithery co-founder Anirudh Kamath into the Arcade team, though neither party disclosed the financial terms of the deal.
Strategic Consolidation in the Agent Ecosystem
While the deal’s scale is modest in terms of market impact, it signals a significant shift in the AI landscape. As enterprises transition agents from experimental pilots to production environments, they require a unified stack: a reliable catalog of tools paired with a runtime capable of authorizing and auditing agent behavior. By acquiring Smithery, Arcade is effectively merging these two critical functions into a single product offering.
Smithery’s primary value proposition was its seamless developer experience, enabling users to find and run an MCP server in just two clicks. This efficiency drove its growth to tens of thousands of entries, encompassing both MCP servers and Anthropic’s Agent Skills format.
Closing the Gap Between Discovery and Execution
Arcade operates at the layer beneath the catalog, providing a “secure action layer” that manages delegated authorization. This ensures agents function as authenticated users with restricted permissions, generating an audit trail for every action. Notably, Arcade claims to have authored the MCP authorization specification currently utilized by major clients and servers.
With $72 million in total funding—bolstered by a $60 million Series A round in June led by SYN Ventures—Arcade possesses the capital to execute this strategy. For a CIO, the pitch is increasingly compelling: a single vendor that identifies the tool, executes it, and validates the user identity associated with the action.
The Data Behind the Tooling Crisis
Arcade’s rationale is grounded in its own diagnostic data. Through its ToolBench benchmark, the company indexed over 43,400 MCP servers and analyzed more than 219,000 tools. Their findings suggest that only 0.5% of these tools meet an “A” grade standard, based on how they behave when triggered by a model.
While these metrics should be viewed with a critical eye—given that Arcade defines the rubric and sells the solution—the underlying observation remains valid. The rapid pace of publishing has outstripped engineering rigor, leading to malformed schemas, missing descriptions, and naming conflicts that frequently cause model hallucinations in production.
Market Dynamics and Competitive Landscapes
Smithery is not the only player in this space. The official MCP Registry, launched in preview in September 2025, serves as a community-owned source of truth designed to be a lightweight reference for downstream catalogs. Meanwhile, Docker has taken a different approach with its MCP Catalog and Toolkit, focusing on containerization, policy enforcement, and secret management.
The distinction lies in trust enforcement. While the official registry verifies metadata and Docker handles process isolation, Arcade aims to control the request path at execution time. This position is vital for security teams needing to track exactly which agent performed which action on behalf of which user.
Navigating New Conflicts and Technical Churn
The acquisition introduces questions regarding neutrality. Developers previously favored Smithery because it was independent of any specific runtime vendor. Now that the catalog is owned by a company with a commercial interest in running those servers, it remains unclear how Arcade will maintain the integrity of ranking, verification, and grading.
Furthermore, the protocol itself is in flux. The July 2026 update introduced breaking changes, such as the removal of the initialize handshake and session identifiers for remote servers. This necessitates constant updates for registries and runtimes alike, potentially rendering older performance grades obsolete.
Key Considerations for Platform Teams
For organizations looking to integrate these tools, three critical questions persist:
- Portability: If tool definitions, authorization policies, and audit logs are locked within Arcade’s control plane, can these artifacts be exported for use in other runtimes without significant rework?
- Independent Grading: Is the ToolBench methodology transparent enough to be reproduced, and how does the company ensure that its grading remains objective when evaluating competitors?
- Pricing at Scale: With Arcade reporting a 25x increase in tool call volume over six months, teams must evaluate how costs will scale as workflows evolve and call volumes spike after model upgrades.
MCP tooling has evolved from a collection of free, community-assembled parts into a procured infrastructure layer. Arcade has moved early to capture this entire chain. While developers will likely retain the speed they enjoyed with Smithery, security teams now face a more consolidated vendor landscape as they work to move AI agents into production.