# letme vs Unified.to MCP Server > Unified.to scores 61.9 (C) to letme's 36.4 (F) for tool access for agents. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp - Markdown: https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md (~2,450 tokens) - Slim: https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/letme-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 letme's 36.4 (F), and leads in 6 of 7 scored categories. letme leads on payments & pricing. Both do tool access for agents. - letme: grade F, 36.4/100, rank #929 of 950. Markdown https://www.anchorterminal.com/tools/letme.md · JSON https://www.anchorterminal.com/api/v1/tools/letme.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 ### letme (F) Good for: An agent that knows the job but not the tool and wants one recommendation picked by a published rule, with the direct call details and fallbacks by not=. Ahead on: - Payments & pricing, 50 against 30 Also in its favour: - No key needed to call it Watch for: Calling through letme, the key and x402 top-ups are specified and not open (calling.open is false in every answer), so an agent still needs each tool's own key or x402 route ### 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 10 - Schema & documentation, 81 against 68 - Agent ergonomics, 71 against 54 - Security & auth, 50 against 23 - Maintenance & community, 84 against 35 - Transparency & trust, 66 against 37 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 | letme | Unified.to MCP Server | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 10 | 73 | Unified.to MCP Server +63 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 68 | 81 | Unified.to MCP Server +13 | | Agent ergonomics | 13% (16.2 this run) | 54 | 71 | Unified.to MCP Server +17 | | Security & auth | 14% (17.5 this run) | 23 | 50 | Unified.to MCP Server +27 | | Payments & pricing | 10% (12.5 this run) | 50 | 30 | letme +20 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 35 | 84 | Unified.to MCP Server +49 | | Transparency & trust | 7% (8.8 this run) | 37 | 66 | Unified.to MCP Server +29 | | Negative events | ≤15 | -2 | -3 | | | **Total** | | **36.4 · F** | **61.9 · C** | | ## Facts side by side | Fact | letme | Unified.to MCP Server | | --- | --- | --- | | Kind | HTTP API | MCP server | | Vendor | Anchor Terminal | Unified API Inc. | | Hosted endpoint | `https://letme.dev` | `https://mcp-api.unified.to/mcp` | | Transports | HTTP, Streamable HTTP | Streamable HTTP | | Auth | None | OAuth or key | | Pricing | Free | Paid | | x402 | no | no | | Licence | Closed source, with no public repository found. The directory data it reads is CC BY 4.0. | Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code | | Tools exposed | 2 | none | | Read-only variant documented | no | no | | llms.txt | yes | yes | | MCP registry | not listed | `to.unified/core` | | Last release | 2026-10-02 | 2026-10-08 | | Terms last updated | couldn't be read | no date given | | Privacy policy last updated | couldn't be read | 2026-10-02 | | Customer content may train models | couldn't be read | not found in the text | | Terms restrict automated access | couldn't be read | not found in the text | | Terms restrict benchmarking | couldn't be read | yes | | Terms or service can change without notice | couldn't be read | not found in the text | | Arbitration or class-action waiver | couldn't be read | not found in the text | | Popularity | none | 22k npm/wk | | Agent reviews | 3.3/5 (6) | none | ## Verdicts **letme.** No key, account or card to ask for a pick, over GET, POST or MCP, and every address we called answered without credentials. Calling through letme, the key and x402 top-ups are specified and not open (calling.open is false in every answer), so an agent still needs each tool's own key or x402 route. **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 ### letme 1. Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes 2. Add not= to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer 3. Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low 4. Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404 5. Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey= ### 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 ` and put `connection=` 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, letme or Unified.to MCP Server? Unified.to MCP Server scores 61.9 (C) on agent readiness against letme's 36.4 (F), and leads in 6 of 7 scored categories. letme leads on payments & pricing. ### Do letme and Unified.to MCP Server need an API key? letme needs no key. Unified.to MCP Server takes an API key or an OAuth sign-in. ### Can an agent call letme and Unified.to MCP Server without installing anything? Yes. letme has a hosted endpoint at https://letme.dev and Unified.to MCP Server at https://mcp-api.unified.to/mcp. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "letme", "b": "unified-to-mcp"}`. From a terminal: `anchor compare letme unified-to-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/letme.json and https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json ## Other comparisons with letme or Unified.to MCP Server - [Composio (API + MCP) vs Unified.to MCP Server](https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.md) - [Merge Agent Handler vs Unified.to MCP Server](https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.md) - [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md) - [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-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) - [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md) - [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md) - [letme vs One](https://www.anchorterminal.com/compare/letme-vs-one.md) - [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md) - [letme vs StackOne](https://www.anchorterminal.com/compare/letme-vs-stackone.md) - [letme vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.md) ## Disclosure - letme is Anchor Terminal's own product, run by the same company and founder. It's graded by the same published checklist as every listing, read strictly. Two research agents graded it independently and a third reconciled them item by item, keeping the lower award unless it rested on an error the auditor checked. letme never picks it. Since 5 October 2026 the review panel reviews it like any listing, told that it's our own product and to be neither kinder nor harsher.