Smithery's proxy shuts down Oct 31: where each server lives now
Smithery's hosted proxy (run.tools and server.smithery.ai) stops on Oct 31, 2026. If your Claude Code, Codex or Cursor config points at those URLs, those servers will stop responding. Below is the official URL or package for each server, taken from the maintainer's own repo or docs. As of our 2026-10-27 audit, no TestedMCP listing points at a Smithery proxy URL.
Smithery's hosted proxy (run.tools, server.smithery.ai) shuts down on October 31, 2026. Search your MCP client config for those two hosts and replace each URL with the vendor's official MCP URL or package. As of our 2026-10-27 audit, no TestedMCP listing points at a Smithery proxy URL.
Last checked 2026-10-27 (America/Chicago). Sources: smithery.ai/future; Smithery proxy audit, Oct 27, 2026; listing fields in scored.json. Related: same MCP servers in Claude Code, Codex and Cursor · Deprecated servers · October 2026 security note.
What Smithery published
From smithery.ai/future, checked 2026-10-27. Quoted exactly:
Smithery's MCP Proxy and managed identity shut down on October 31.
On October 31, 2026, we're shutting down Smithery's connection management services. Smithery will remain as a public (non-proxied) MCP registry.
Under “What stops working on October 31” the page lists:
Server URLs on run.tools and server.smithery.ai(among API, accounts, CLI and SDKs).Using a server yourself? Switch to the vendor's official MCP URL. Smithery URLs stop working on October 31, and connecting through Smithery won't be possible after that. You can find the official URL on the server's page on smithery.ai.
Re-scan of TestedMCP data (2026-10-27)
We searched every listing field and data/*.json for run.tools and server.smithery.ai connect URLs, and matched that against the 2026-10-27 audit file (Smithery proxy audit, Oct 27, 2026), which recorded 0 proxy URLs. A build-time test fails the site build if any published /tools/<slug>/ page links to those hosts.
Published listings still pointing at the proxy
Flagged listing count: 0. Names: none.
| Listing | Official URL or package | Source (checked 2026-10-27) |
|---|---|---|
None. Re-scan of listing data on 2026-10-27 found 0 published listings pointing at run.tools or server.smithery.ai. | ||
Listings that mention Smithery in our data (not proxy URLs)
These are directory or introspection mentions only. They are not run.tools / server.smithery.ai connect URLs. Official package or repo is taken from scored.json.
| Listing | Official URL or package | Note |
|---|---|---|
| Mistral MCP (community, Swih) | https://github.com/Swih/mistral-mcpnpm package mistral-mcp | stderr mentions Smithery as a directory for sandboxed introspection (Glama, Smithery, etc.); not a connect URL (see audit). Source: scored.json repo Swih/mistral-mcp; our raw test results; Smithery proxy audit, Oct 27, 2026. |
Vendor official MCP URLs already on remote listings
Smithery's notice says to switch to each vendor's official MCP URL. These 20 remote listings already store a vendor endpoint in scored.json (checked 2026-10-27). They are listed here as the official URLs we record, not as proof that each one used a Smithery proxy.
MCP endpoint URLs below are shown as plain code for pasting into an MCP client config (Claude Code, Codex, Cursor, etc.). They are not web pages, so they are not linked.
| Listing | Official MCP URL | Source (checked 2026-10-27) |
|---|---|---|
| Airbyte MCP (official, remote) | https://mcp.airbyte.com/mcp | scored.json endpoint |
| Algolia Productivity MCP (official, remote) | https://mcp.algolia.com/mcp | scored.json endpoint |
| Basecamp MCP (official, remote) | https://mcp.basecamp.com/mcp | scored.json endpoint |
| DeployHQ MCP (official, remote) | https://mcp.deployhq.com/mcp | scored.json endpoint |
| Fly.io MCP (official, remote) | https://mcp.fly.io | scored.json endpoint |
| Framer MCP (official, remote) | https://mcp.framer.com/mcp | scored.json endpoint |
| GitLab MCP (official, remote) | https://gitlab.com/api/v4/mcp | scored.json endpoint |
| HutchDB MCP (official, remote) | https://app.hutchdb.com/api/mcp | scored.json endpoint |
| Linear MCP (official, remote) | https://mcp.linear.app/mcp | scored.json endpoint |
| Make MCP (official, remote, v2) | https://mcp.make.com/v2 | scored.json endpoint |
| Meta Ads MCP (official, remote) | https://mcp.facebook.com/ads | scored.json endpoint |
| Mollie MCP (official, remote) | https://mcp.mollie.com/mcp | scored.json endpoint |
| MongoDB Atlas Managed MCP (official, remote) | https://mcp.mongodb.com | scored.json endpoint |
| SavvyCal MCP (official, remote) | https://savvycal.com/mcp | scored.json endpoint |
| ScrapingBee MCP (official, remote) | https://mcp.scrapingbee.com/mcp | scored.json endpoint |
| Suno MCP (official, remote, beta) | https://api.suno.com/mcp | scored.json endpoint |
| Synorb MCP (official, remote) | https://mcp.synorb.com/mcp | scored.json endpoint |
| Teamwork.com MCP (official, remote) | https://mcp.ai.teamwork.com | scored.json endpoint |
| Vercel MCP (official, remote) | https://mcp.vercel.com | scored.json endpoint |
| Xero Remote MCP (official) | https://api.xero.com/mcp/v1 | scored.json endpoint |
If your client still uses a Smithery proxy URL
- Replace
*.run.toolsorserver.smithery.ai/…with the vendor's official MCP URL or local package (per smithery.ai/future). - For a server we list, open the directory or
/tools/<slug>/for the endpoint, npm/PyPI package, or GitHub repo we tested. - Config file layout differs by client: see same MCP servers in Claude Code, Codex and Cursor.
- Registry-deprecated packages are on Deprecated servers.
- Background and audit summary: Smithery MCP proxy shutdown on the October 2026 security page.
FAQ
Is Smithery shutting down?
Smithery's MCP Proxy and managed identity shut down on October 31, 2026, per smithery.ai/future (checked Oct 27, 2026). The same page says smithery.ai remains as a public, non-proxied MCP registry powered by Arcade.dev. Hosts that stop: run.tools and server.smithery.ai.
What replaces run.tools URLs?
Use the vendor's official MCP URL or package. smithery.ai/future says: Switch to the vendor's official MCP URL. On TestedMCP, open the listing under /tools/<slug>/ for the endpoint, npm/PyPI package, or GitHub repo we recorded. As of the 2026-10-27 audit, no TestedMCP listing pointed at a Smithery proxy URL.
How do I check if my MCP config uses a Smithery proxy URL?
Search your Claude Code, Codex or Cursor MCP config for run.tools and server.smithery.ai. Any server URL on those hosts stops working on October 31, 2026; replace it with the vendor's official MCP URL or package.
What this page does not claim
- We did not probe third-party client configs outside this repo.
- We did not crawl smithery.ai to build a full directory of every server that ever used the proxy.
- A listing on TestedMCP is not a security review of that server.
Sources (accessed 2026-10-27)
- Smithery: The future of Smithery
- scored.json (listing endpoint, repo, package name)
- our raw test results (error-output mentions; not published on /data/)
- Smithery proxy audit, Oct 27, 2026 (repo audit record; not published on /data/)
- /security/2026-10/#smithery-proxy
Checked 2026-10-27