Home › MCP servers › Moving off Smithery

Moving off Smithery before October 31, 2026

Smithery says its MCP proxy, API, accounts, API keys, CLI and SDKs stop working on October 31, 2026, and that it stays on as a public, non-proxied registry. If you connect through a Smithery URL, switch to the vendor's official MCP URL before then. Below: what changes, your options, and a checklist.

New to MCP? See what an MCP server is.

What is changing at Smithery on October 31, 2026?

Smithery says it is shutting down its connection management services on October 31, 2026. Server URLs on run.tools and server.smithery.ai stop working, and so do the Smithery API, Connect, Toolbox, accounts, API keys, CLI and SDKs. What stays is smithery.ai as a public, non-proxied MCP registry, now powered by Arcade.dev, with a curated set of verified servers whose pages show direct MCP URLs.

Who owns Smithery now?

Arcade.dev said on August 5, 2026 that it had acquired Smithery, and Smithery's notice is signed by its cofounder as 'now part of Arcade'. The notice itself gives no reason for ending the connection services, so we give none either.

What happens to paid plans?

Smithery says it is refunding every charge since August 5 and cancelling subscriptions going forward, so nobody on a paid plan is charged again. It says refunds usually show up within 5 to 10 business days. Anything beyond that, such as refunds for earlier charges, is not covered by the notice.

What does it mean if you use Smithery-hosted MCP servers?

Smithery's notice splits it three ways. If you use a server yourself, switch to the vendor's official MCP URL, which you can find on the server's smithery.ai page; connecting through Smithery won't be possible after October 31. If you want ready-made tools like Gmail or Slack, it points to Arcade. If you manage MCP connections for your own users, you need a replacement before October 31. See remote MCP servers and their URLs.

What if you published a server on Smithery?

Smithery's notice says only that URLs on run.tools and server.smithery.ai stop working and that a curated set of verified servers will show direct MCP URLs. It does not say how other listings are handled, and we could not verify that. If you publish a server, check your listing page and ask Smithery directly.

What are your options after Smithery?

It depends on what you used Smithery for. To connect to a server, use the vendor's official MCP URL. To publish one, the Official MCP Registry is the open route, and Glama and mcp.so each have a submit path. PulseMCP has paused submissions. For managed connections, Smithery points to Arcade. The table shows what we verified. Compare the registries by size, fee and status in MCP marketplaces and registries compared.

Listings on DartzDabz are free: submit a tool.

Is PulseMCP an option right now?

Not for new submissions. PulseMCP's submit page says submissions and changes to existing listings are paused, with no promised reopening date, and its page was last updated September 3, 2026. Its home page banner still said the pause continues on October 23, 2026. It tells publishers to use the Official MCP Registry and says it will pick listings up from there once it is back.

What does the Official MCP Registry need from a remote server?

The registry's docs say a remote MCP server must be publicly accessible at the URL you publish, and the entry lists it under a remotes property in server.json. The registry hosts only metadata, not the server itself, and it is in preview, so breaking changes or data resets may occur before general availability.

What is a checklist for moving off Smithery?

Seven steps cover it: find every Smithery URL you use, swap each for the vendor's official URL, replace anything tied to a Smithery account, line up a replacement if you manage connections for users, check any server you published, and confirm any refund. Do the first three before October 31, 2026.

1. List every Smithery URL you use. Search your MCP client configs, scripts and CI for URLs on run.tools or server.smithery.ai, and for the Smithery CLI, SDK, Connect or Toolbox. Smithery says all of these stop working on October 31, 2026.
2. Find each vendor's official URL. Open the server's page on smithery.ai. Smithery says verified servers' pages will show the direct MCP URL. If there is none, check the vendor's own documentation.
3. Swap the URL and test. Replace the Smithery URL in your client config with the vendor's URL, restart the client and run one real tool call. Your client may ask you to sign in with the vendor; Smithery's notice does not cover that, so check the vendor's docs.
4. Replace anything that used a Smithery account. Smithery accounts and API keys stop working too, so move any script or service that authenticated through Smithery before the cutoff.
5. If you manage connections for users, pick a replacement now. Smithery says you need a replacement before October 31 and that its team will help you work out the right one, even if it is not Arcade.
6. If you published a server, check your listing. Publish to the Official MCP Registry, which hosts metadata only, and check your Smithery page. Smithery's notice does not say what happens to listings outside its curated verified set.
7. If you paid Smithery, check for the refund. Smithery says it is refunding every charge since August 5 and cancelling subscriptions, and that refunds usually show up within 5 to 10 business days.

How can DartzDabz help you choose MCP servers after Smithery?

Before you point your setup at a new URL, check the server. As of October 25, 2026, DartzDabz lists 1,578 MCP servers and gives 1,327 of them an automated trust and uptime score, refreshed daily from live checks of the server itself. Scores are point-in-time checks, not endorsements or security audits. We honor robots.txt, so servers that opt out show as opted out instead of getting a score.

Browse MCP servers with daily trust scores and read how the trust score works. Want a short list? See the best MCP servers.

What could we not verify?

Smithery's notice carries no date, so we cannot say when it was posted. It does not say how listings outside its curated verified set are handled, or how many servers stay. We did not test any hosting route or any registry's submit flow. We have no search volume data for these questions. We did not verify how many of the MCP servers in our own directory point at Smithery URLs.

See real agent setups you can copy, or browse the agent tool directory.

Building on Grok Bot? Start a crew from the DartzDabz Crew Builder template.

We may be paid by X based on how many people use our Crew Builder template.