GUIDE · SMITHERY SHUTDOWN

A Smithery alternative for finding MCP servers

Smithery is shutting down its MCP proxy, API, CLI and server URLs on 31 October 2026. If you used Smithery to find and install MCP servers, MCPfinder gives your agent a search across the Official MCP Registry and Glama, and returns each server’s own package or URL instead of a proxy.

What Smithery keeps and what stops on 31 October

From Smithery’s own announcement (smithery.ai/future, checked 21 October 2026):

  • Stops working: server URLs on run.tools and server.smithery.ai; the Smithery API, Connect and Toolbox; Smithery accounts and API keys; the Smithery CLI and SDKs (current versions will be marked deprecated).
  • Stays: smithery.ai as a public, non-proxied directory of MCP servers, now powered by Arcade.dev, with a curated set of verified servers whose pages show direct MCP URLs.
  • Smithery’s advice: switch to the vendor’s official MCP URL before 31 October.

Discovery and install configs, not hosting

Covered: search

Your agent calls search_mcp_servers over one index built from the Official MCP Registry and Glama (over 100,000 servers in the October 2026 snapshot).

Covered: direct install config

get_install_config returns the server’s own package command or the remote endpoint from its registry entry, shaped for Claude, Cursor, Claude Code, Cline or Windsurf. No Smithery or run.tools URLs.

Not covered: hosted proxy

MCPfinder does not run servers for you. Local servers run on your machine; remote servers are reached at the URL published in their registry entry.

Not covered: managed OAuth

There is no Connect-style identity layer. If you manage MCP connections for your own users, you need a separate service for that.

Replace a Smithery URL in three steps

01

Install MCPfinder

Add npx -y @mcpfinder/server to your client’s MCP config. No account or API key.

02

Find the server again

Ask your agent for the server by name, e.g. “find the Linear MCP server”. Then inspect its trust signals, tools and env vars.

03

Swap the config

Replace the server.smithery.ai or run.tools entry with the snippet from get_install_config. If no install method is known, MCPfinder says so and links the listing and repository.

Common questions

What is changing at Smithery on 31 October 2026?
According to Smithery’s announcement (smithery.ai/future, checked 2026-10-21), server URLs on run.tools and server.smithery.ai, the Smithery API, Connect, Toolbox, accounts, API keys, the CLI and the SDKs stop working on 31 October 2026. smithery.ai stays online as a public, non-proxied directory, now powered by Arcade.dev.
Is MCPfinder a drop-in replacement for Smithery?
No. MCPfinder does not host or proxy MCP servers and does not manage OAuth connections, so it does not replace Smithery Connect or the hosted proxy. It replaces the discovery part: an agent searches the Official MCP Registry and Glama through MCPfinder and gets an install config for the server itself.
How do I replace a server.smithery.ai or run.tools URL?
Switch to the vendor’s own MCP URL or package, as Smithery recommends. Ask MCPfinder to search for the server and call get_install_config: it returns the package command (for example npx or uvx) or the remote endpoint published in the server’s registry entry. If no install method is known, it says so and links the listing and repository.
Does MCPfinder still use Smithery data?
No. Since MCPfinder 2.0 (October 2026) the index is built from the Official MCP Registry and Glama only, and registry.smithery.ai, server.smithery.ai and run.tools endpoints are filtered out of install configs.
Is MCPfinder free?
Yes. It is open source under AGPL-3.0 and runs locally with npx -y @mcpfinder/server. There is no account or API key.

Related MCP finder pages

Let your agent find the right MCP

Install MCPfinder once. Search registries, inspect trust signals, and paste client-ready config.