Smithery's proxy shut down: the official URL for each MCP server

What happened

On October 31, 2026 Smithery shut down its MCP proxy and managed identity. Server URLs on server.smithery.ai and run.tools, the Smithery API, Connect, Toolbox, accounts and API keys, and the CLI and SDKs stopped working. Smithery is now a directory, part of Arcade, that points to each vendor's official MCP URL (Smithery's notice).

If an MCP server in your Claude, Cursor or VS Code config stopped connecting on November 1, check its URL. If it starts with https://server.smithery.ai/ or ends in run.tools, it was going through the proxy. You need the vendor's own endpoint instead.

How to switch

1. Find the server in the table below, or on the vendor's own docs if it is not listed.
2. Replace the URL in your client config. For a remote server it usually looks like { "url": "https://vendor.example/mcp" }.
3. If the table says a key is needed, create one in the vendor's dashboard. Smithery API keys no longer work anywhere, so you need the vendor's own key, sent as the header the vendor documents.
4. Prefer a local install instead? Most of these servers also publish an npm or PyPI package; the install guide on each listing shows both.

Official endpoints we checked

75 servers with a vendor-hosted endpoint that answered our last health check, 22 of them need an API key. The list comes from the official MCP registry and is rebuilt with our catalog (last rebuilt Nov 1, 2026). A 401 or 405 counts as answering: it means the endpoint is up and wants a key or a POST. Inclusion is not a review; servers we have reviewed by hand are on the marketplace.

Not in the table?

Many servers on Smithery were community builds with no vendor-hosted endpoint; for those the only path now is to run them locally from their package or repo. Check the server's GitHub README for an official remote URL first, and be wary of third-party URLs that appeared after the shutdown claiming to replace the proxy: they see every request and every key you send through them.

Maintain one of these servers and your endpoint is missing or wrong? Claim your listing and it updates on the next rebuild. Daily monitoring of the endpoint is part of Maintainer Pro.

Related

• CuratedMCP vs Smithery, updated for the shutdown
• How to choose a secure MCP server