Smithery hosting has ended. Here is where to move.
Smithery joined Arcade, and on 31 October 2026 its hosted server URLs, API, accounts and API keys were shut down. What remains is a public, non-proxied MCP registry. If your MCP server ran on Smithery, it needs a new home and a new URL.
Free: 1 project, no credit card. 5 project slots €39/month, €5 per extra slot.
Side by side
Spec
DenkOps
Smithery
Hosts MCP servers
Yes, always-on slot per project
No longer: hosted URLs shut down 31 Oct 2026
Registry / directory
No, list your URL in public registries
Yes, a public non-proxied MCP registry (run by Arcade)
OAuth for MCP
Built in with "connector": true
Not applicable after the shutdown
Runtimes
Bun (TypeScript/JS), Python
Not applicable
Logs, secrets, rollbacks
Yes, also over MCP for your coding agent
Not applicable
Pricing
1 project free; 5 slots €39/month, €5 per extra slot
Paid charges since 5 Aug 2026 are being refunded
Facts about Smithery come from its official documentation, checked November 2026. Sources are listed at the bottom of this page.
Move a Smithery-hosted server in four steps
Get the code running locally. Smithery-hosted servers were usually stdio servers wrapped for HTTP. Make sure your server speaks Streamable HTTP, with the official SDK or defineMcp from @denkopsai/sdk/mcp, which serves it for you.
Move secrets into environment variables. Anything you configured in Smithery becomes a DenkOps environment variable. Never commit keys.
Turn on sign-in if your users had accounts. Set "connector": true in denkops.json for OAuth with Google, GitHub or Microsoft, and an allowed-email list if needed. See OAuth for MCP servers.
Deploy and update your clients. Say "deploy on DenkOps" in your coding agent. Give users the new URL, or put it on your own domain so the next move never changes it. The config generator prints the new config for every client, and the MCP server checker confirms it works before you announce it.
Keep a URL you control
The lesson from a platform shutdown is to keep the URL on your own domain. DenkOps supports a custom domain per connector, so clients keep working wherever the server runs next.
Which one fits
Choose DenkOps when
Your server ran on Smithery's hosting and you need a stable HTTPS URL again
Your users signed in to your server and you want OAuth handled for you
You want logs and redeploys your coding agent can drive
Choose Smithery when
You only want your server listed in a public registry and you host it yourself
You are moving to Arcade's tooling for agent authorization
FAQ
Does Smithery still host MCP servers?
No. According to Smithery, hosted server URLs, the Smithery API, accounts and API keys were shut down on 31 October 2026. A public, non-proxied registry remains.
Can I keep using the Smithery registry?
The registry lists servers that you host yourself. You can host the server on DenkOps and keep a registry listing pointing at your new URL.
How long does a move to DenkOps take?
For a server that already speaks Streamable HTTP, usually one deploy. Servers that only spoke stdio need an HTTP transport first, which defineMcp provides.
