Smithery vs Glama
Product engineer: Use Glama to check whether your server is listed and graded. Developer-platform lead: Do not plan new hosting on Smithery; Glama's data license affects reuse. Agent builder: Glama's connector filters (No Auth, OAuth 2.0, health) are the faster way to find a working remote.
The sourced difference
Smithery shut down its MCP Proxy and managed identity on 31 Oct 2026 after joining Arcade, and its listing URLs return 404; Glama still lists 115,804 servers and 40,288 remote connectors with grades, but its API needs a key and attribution. (Smithery: smithery.ai home page, read 5 November 2026 and Arcade: Smithery is now part of Arcade.dev (5 Aug 2026), read 5 November 2026; Glama: Glama MCP servers directory, counted on 4 November 2026 and Glama MCP connectors (remote servers), counted on 4 November 2026)
Verdicts by reader
| Reader | Verdict |
|---|---|
| Product engineer | Use Glama to check whether your server is listed and graded. |
| Developer-platform lead | Do not plan new hosting on Smithery; Glama's data license affects reuse. |
| Agent builder | Glama's connector filters (No Auth, OAuth 2.0, health) are the faster way to find a working remote. |
Side by side on the rubric
| Dimension | Smithery | Glama |
|---|---|---|
| Remote transport | Streamable HTTP (registry entries) | lists both |
| OAuth with client registration | managed identity retired | filter only |
| Per-tool auth scoping | not documented | not documented |
| Hosting and scale limits | proxy retired | not published |
| Observability | not documented | health status on listings |
| Pricing | not published | not detailed |
| Registry submission | unclear after acquisition | open, Add Server button |
| Discoverability by agents | catalog browse only | API with key and attribution |
| Own server in the registries | no own server found | not found |
Evidence for every cell is on the profiles: Smithery and Glama.