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.
From Smithery’s own announcement (smithery.ai/future, checked 21 October 2026):
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).
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.
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.
There is no Connect-style identity layer. If you manage MCP connections for your own users, you need a separate service for that.
Add npx -y @mcpfinder/server to your client’s MCP config. No account or API key.
Ask your agent for the server by name, e.g. “find the Linear MCP server”. Then inspect its trust signals, tools and env vars.
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.
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.npx -y @mcpfinder/server. There is no account or API key.Install MCPfinder once. Search registries, inspect trust signals, and paste client-ready config.