# Smithery vs Unified.to MCP Server

> Unified.to scores 61.9 (C) to Smithery's 50.7 (D) for app automation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp
- Markdown: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Unified.to MCP Server scores 61.9 (C) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Both do app automation.

- Smithery: grade D, 50.7/100, rank #766 of 950. Markdown https://www.anchorterminal.com/tools/smithery.md · JSON https://www.anchorterminal.com/api/v1/tools/smithery.json
- Unified.to MCP Server: grade C, 61.9/100, rank #455 of 950. Markdown https://www.anchorterminal.com/tools/unified-to-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json
- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md
- All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md

## Which one, for what

### Smithery (D)

Good for: A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.

Watch for: No terms of service are linked from the site, the docs or the footer. The privacy notice of 20 June 2025 is the only legal document found

### Unified.to MCP Server (C)

Good for: A B2B software team that already uses or plans to use Unified's API and wants the same customer connections exposed to an LLM, with data read live from the source app.

Ahead on:
- Reliability, 73 against 60
- Schema & documentation, 81 against 76
- Agent ergonomics, 71 against 65
- Payments & pricing, 30 against 10
- Maintenance & community, 84 against 43
- Transparency & trust, 66 against 46

Watch for: The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account


## Score by category

| Category | Weight | Smithery | Unified.to MCP Server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 73 | Unified.to MCP Server +13 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 76 | 81 | Unified.to MCP Server +5 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 71 | Unified.to MCP Server +6 |
| Security & auth | 14% (17.5 this run) | 50 | 50 | even |
| Payments & pricing | 10% (12.5 this run) | 10 | 30 | Unified.to MCP Server +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 43 | 84 | Unified.to MCP Server +41 |
| Transparency & trust | 7% (8.8 this run) | 46 | 66 | Unified.to MCP Server +20 |
| Negative events | ≤15 | -2 | -3 | |
| **Total** | | **50.7 · D** | **61.9 · C** | |

## Facts side by side

| Fact | Smithery | Unified.to MCP Server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Smithery (Arcade.dev) | Unified API Inc. |
| Hosted endpoint | `https://api.smithery.ai` | `https://mcp-api.unified.to/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary hosted service, with no terms of service found. The CLI (`smithery`) is AGPL-3.0, the TypeScript client (`@smithery/api`) is Apache-2.0 and the credential layer agent.pw is MIT | Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `to.unified/core` |
| Last release | 2026-07-20 | 2026-10-08 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | 2025-06-20 | 2026-10-02 |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | yes |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | not found in the text |
| Popularity | 840 stars, 2.7k npm/wk | 22k npm/wk |

## Verdicts

**Smithery.** Service tokens can be limited by namespace, resource, operation and connection metadata, with a lifetime of at most 24 hours. No terms of service, rate limits or SLA were found, the pricing page could not be read, and the newest client release is from 20 July 2026.

**Unified.to MCP Server.** Every previewed tool carries a typed input schema and read-only, destructive and idempotent annotations, and the list can be narrowed by permission or tool name. The default credential is a workspace API key that reaches every connection, and the SSE transport was removed on 23 September 2026 in the changelog entry that announced it.

## Before you call either

### Smithery

1. Keep the API key on the backend and hand an agent a service token limited to `connections` with `read` and `execute` and a `metadata` match
2. Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool
3. On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId`
4. Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories`
5. Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them

### Unified.to MCP Server

1. Use the host for the workspace's region. US is `mcp-api.unified.to`, EU is `mcp-api-eu.unified.to` and AU is `api-au.unified.to`. A credential on another region's host resolves to not found
2. Send the key as `Authorization: Bearer <key>` and put `connection=<id>` in the URL. Without `connection` the server lists workspace management tools, not the customer's data tools
3. Pass `tools` or `permissions` in the URL before listing. An unfiltered connection can list dozens of tools with large output schemas
4. Expect HTTP 429 on tool calls since 23 September 2026. Unified does not queue or retry, so back off and retry yourself
5. Page with `limit` (100 at most on most endpoints) and `offset`, and stop when a page returns fewer records than `limit`

## Questions

### Which is better for AI agents, Smithery or Unified.to MCP Server?

Unified.to MCP Server scores 61.9 (C) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories.

### Do Smithery and Unified.to MCP Server need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Smithery and Unified.to MCP Server without installing anything?

Yes. Smithery has a hosted endpoint at https://api.smithery.ai and Unified.to MCP Server at https://mcp-api.unified.to/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "smithery", "b": "unified-to-mcp"}`. From a terminal: `anchor compare smithery unified-to-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/smithery.json and https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json

## Other comparisons with Smithery or Unified.to MCP Server

- [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md)
- [Composio (API + MCP) vs Unified.to MCP Server](https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.md)
- [Merge Agent Handler vs Smithery](https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.md)
- [Merge Agent Handler vs Unified.to MCP Server](https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.md)
- [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md)
- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)
- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)
- [Smithery vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.md)
- [StackOne vs Unified.to MCP Server](https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.md)
- [Unified.to MCP Server vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp.md)
- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md)
- [letme vs Unified.to MCP Server](https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md)