{ "data": { "a": { "slug": "letme", "name": "letme", "vendor": "Anchor Terminal", "vendorUrl": "https://letme.dev", "kind": "http-api", "category": "aggregator", "summary": "letme.dev selects tools for a task using Anchor Terminal's grades.", "url": "https://www.anchorterminal.com/tools/letme", "markdownUrl": "https://www.anchorterminal.com/tools/letme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/letme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/letme.json", "license": "Closed source, with no public repository found. The directory data it reads is CC BY 4.0.", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://letme.dev", "packages": [], "auth": "none", "authNotes": "Asking for a pick needs no key and no account. A self-issued letme key for calling through letme is specified on /letme/#key and not issued yet.", "pricing": "free", "pricingNotes": "Picking is free and needs no key. Calling through letme, at the vendor's own price with partner vendors paying 15 per cent of what they bill, comes later (https://www.anchorterminal.com/letme/#costs).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No payments yet. Top-ups by x402 are specified for when calling through letme opens (https://www.anchorterminal.com/letme/#pay).", "endpoints": [] }, "toolCount": 2, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-02" }, "docsUrl": "https://www.anchorterminal.com/letme/", "llmsTxt": "https://letme.dev/llms.txt", "openapi": "https://letme.dev/openapi.json", "capabilities": [ "agent.tools" ], "tags": [ "hosted", "free", "no-signup", "mcp", "llms-txt", "uk" ], "lastRelease": "2026-10-02", "graded": true, "own": true, "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.", "anchor": { "graded": true, "score": 36.4, "grade": "F", "agentReady": false, "rank": 929, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 35, "payments": 50, "reliability": 10, "schema": 68, "security": 23, "transparency": 37 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-02" }, "negative": -2, "negativeNotes": [ "2026-10-02, -2. For speech.stt the answer's why says \"price couldn't be compared (no two listings at grade BB publish a price for the job in the same unit)\" while the same answer gives all four BB listings a lead price per audio-minute ($0.00167, $0.0024, $0.002 and $0.003). It then picks by overall score (77 against 73.6). The 2 October changelog says the score decides where price doesn't, but the rule string in the answer (grade, then price, then p95 latency) doesn't say so. Azure is also the cheapest of the four, so the pick wouldn't change. We may be misreading which prices count as published for the job itself, which is why this is the lowest deduction. Reproduced on directory build 20261002T161644Z. Source https://letme.dev/speech.stt.json?n=10\u0026minGrade=BB" ], "verdict": "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.", "bestFor": "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=.", "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.", "strengths": [ "No key, account or card to ask for a pick, over GET, POST or MCP, and every address we called answered without credentials", "OpenAPI 3.1, llms.txt and an Agent Skill linked from llms.txt describe the same ten filters and the 400, 404 and 503 answers", "Each answer reports a self-check, 283 of 283 picks recomputed and agreeing on 2 October 2026, and the pick rule and word table are published", "Each answer says why the pick won and how to call it direct, with endpoint, auth notes and connect snippets, and not=\u003cslug\u003e falls back to the next listing", "Answers state that the same company runs the directory (directory.sameCompany is true)" ], "weaknesses": [ "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", "No status page, no published rate limit for picking, no 429 guidance and no SLA, and the limits on /letme/ belong to a key that isn't issued", "Closed source, no SDK and no MCP registry entry, and the GitHub link on /letme/ and /about/ answers 404", "On 2 October 2026 the speech.stt answer said price couldn't be compared while listing four same-grade prices per audio-minute", "Run by the company that grades the tools it picks from, with no stated logging for picks, no subprocessors and no deprecation policy for letme.dev" ], "agentNotes": [ "Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes", "Add not=\u003cslug\u003e to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer", "Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low", "Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404", "Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey=\u003ckey\u003e" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 6, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 36.4 } ], "editorialScores": { "ergonomics": 54, "maintenance": 35, "payments": 50, "reliability": 10, "schema": 68, "security": 23, "transparency": 15 }, "provenanceScore": 59 }, "connect": { "http": "curl -s https://letme.dev/web.search" }, "letme": { "capability": "https://letme.dev/agent.tools" }, "area": "business", "provenance": { "legalEntity": "Anchor Terminal Ltd", "domain": "letme.dev", "domainRegistered": "2026-09-30", "endpointOnVendorDomain": true, "terms": "https://www.anchorterminal.com/about/#terms", "privacy": "https://www.anchorterminal.com/about/#privacy", "statusPage": "", "changelog": "https://www.anchorterminal.com/changelog/", "securityTxt": "none", "checked": "2026-10-02", "notes": [ "Run by Anchor Terminal Ltd, the company that runs this directory. Terms, privacy and the changelog are Anchor Terminal's own pages.", "letme.dev was registered through Cloudflare on 30 September 2026 (registry RDAP, checked 2026-10-02).", "No status page. letme.dev/status and anchorterminal.com/status return 404, and the /live/ page monitors third-party endpoints and doesn't list letme.dev.", "letme.dev/.well-known/security.txt returns 404. anchorterminal.com/.well-known/security.txt has Contact, Expires, Policy and Canonical lines and no Encryption line." ], "score": 59 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/letme.json", "live": { "slug": "letme", "probe": { "target": "https://letme.dev", "method": "get", "lastAt": "2026-10-10T03:53:32.434958613Z", "lastOk": true, "lastStatus": 200, "lastMs": 24, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 86, "samples24h": 249, "samples30d": 2017, "days": [ { "date": "2026-10-02", "probes": 100, "ok": 100 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "securityTxt": { "url": "https://letme.dev/.well-known/security.txt", "state": "valid", "expires": "2027-10-01T00:00:00.000Z", "checkedAt": "2026-10-09T15:39:14.501273753Z" }, "llmsTxt": { "url": "https://letme.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:13.861275005Z" }, "domain": { "domain": "letme.dev", "registered": "2026-09-30", "source": "https://pubapi.registry.google/rdap/domain/letme.dev", "checkedAt": "2026-10-04T13:08:23.055142711Z" }, "pages": [ { "url": "https://www.anchorterminal.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:48:03.41970721Z", "changedAt": "2026-10-09T18:48:03.41970721Z", "fingerprint": "60507c20305f" }, { "url": "https://www.anchorterminal.com/about/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:48:01.365110198Z", "changedAt": "2026-10-09T18:48:01.365110198Z", "fingerprint": "d034cf6a23fd" } ], "updatedAt": "2026-10-10T03:53:32.434958613Z" } }, "answer": "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 \u0026 pricing.", "b": { "slug": "unified-to-mcp", "name": "Unified.to MCP Server", "vendor": "Unified API Inc.", "vendorUrl": "https://unified.to", "kind": "mcp", "category": "aggregator", "summary": "Unified.to MCP Server is a hosted Streamable HTTP server from Unified API Inc. that turns one end-customer connection to a business app into MCP tools, on top of the vendor's unified API for CRM, HR, accounting and other categories.", "url": "https://www.anchorterminal.com/tools/unified-to-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/unified-to-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/unified-to-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json", "repo": "https://github.com/unified-to/unified-mcp-typescript", "license": "Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp-api.unified.to/mcp", "packages": [ { "registry": "npm", "name": "@unified-api/typescript-sdk" } ], "auth": "mixed", "authNotes": "Self-serve. A person signs in to app.unified.to with Google or GitHub and copies a workspace API key. Sent as `Authorization: Bearer \u003ckey\u003e` with `connection=\u003cid\u003e` in the URL, it lists that connection's tools, and without a connection it lists workspace management tools. The docs warn that the key reaches every connection and the whole account. The management tool `get_unified_connection_mcp_url` in `user` mode returns a URL with a signed token limited to one connection. Enterprise-managed authorisation exchanges an identity provider's assertion at `POST /oauth/token` for an `ema_` token that lasts 3,600 seconds and carries category read and write scopes. Unified turns it on per workspace on request. `?token=` still works for keys and is marked deprecated.", "pricing": "paid", "pricingNotes": "Plans from $750 a month. Grow is $750+ with 750,000 API calls and $1.00 per 1,000 beyond that, Pro $1,500+ with 2,000,000 and $0.75, Scale $3,000+ with 6,000,000 and $0.50, and Enterprise is priced on contract. Each MCP tool call counts as one API request, and the FAQ says successful calls are billable. A tester account starts with 2,500 free API requests and Grow and Pro start with a 30-day free trial. The page does not say whether a card is needed (https://unified.to/pricing, checked 2026-10-09).", "priceSummary": "$750 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the MCP docs pages, the pricing page or the Terms of Service (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 22019, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.unified.to/mcp/overview", "llmsTxt": "https://docs.unified.to/llms.txt", "openapi": "https://api.unified.to/openapi.json", "registryName": "to.unified/core", "capabilities": [ "automation.apps", "automation.auth", "automation.actions", "agent.tools", "automation.webhooks" ], "tags": [ "hosted", "mcp", "paid", "free-trial", "api-key", "openapi", "llms-txt", "typescript", "python", "status-page", "soc2", "mcp-registry", "closed-source", "data-residency" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 61.9, "grade": "C", "agentReady": false, "rank": 455, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 84, "payments": 30, "reliability": 73, "schema": 81, "security": 50, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "23 September 2026. The MCP changelog entry of that date removed the SSE transport (`/sse` and `/sse/messages` now return HTTP 410), dropped `sse_url` from the `get_unified_connection_mcp_url` response, which the docs label a breaking change, and stopped regions resolving across one another. No earlier notice was found in the MCP changelog, the site changelog or the September product update. Whether customers were told privately was not established. The migration is a one-word URL change and is documented, so 3 points (https://docs.unified.to/mcp/changelog)." ], "verdict": "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.", "bestFor": "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.", "strengths": [ "A credential-free preview of the HubSpot tool list returned 78 tools, each with a JSON Schema input and `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations, and 66 with an output schema", "The `permissions` and `tools` URL parameters limit which tools a connection lists, and `hide_sensitive` strips names, emails and telephone numbers from results", "A `user` mode URL carries a signed token limited to one connection, so the workspace API key need not be shared with an end customer", "Rate limits are published per plan, from 500 requests a minute on Test to 10,000 on Scale, shared across the workspace", "The privacy policy has an MCP section. It says end-customer data is not stored or cached and that Unified does not train models on any data", "The MCP changelog is dated and had entries on 22 July, 21 and 23 September and 8 October 2026" ], "weaknesses": [ "The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account", "The `/sse` transport and the `sse_url` response field were removed on 23 September 2026. No earlier notice was found in the MCP changelog, the site changelog or the September update", "The connection-scoped signed token travels in the URL as `?token=`. The docs mark `?token=` authentication as deprecated, with no end date set", "One HubSpot connection lists 78 tools whose definitions come to about 133 KB without output schemas and 343 KB with them", "No uptime SLA is published. The pricing page says SLAs come with a custom Enterprise plan", "No security.txt, bug bounty or disclosure policy was found, and the security page gives February 2025 as its last review", "The Terms of Service forbid probing, scanning or testing the vulnerability of the service. This matters before any probe is run", "The Terms of Service bar transmitting financial or medical information and birth dates through the service, while the product sells accounting and HR integrations" ], "agentNotes": [ "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", "Send the key as `Authorization: Bearer \u003ckey\u003e` and put `connection=\u003cid\u003e` in the URL. Without `connection` the server lists workspace management tools, not the customer's data tools", "Pass `tools` or `permissions` in the URL before listing. An unfiltered connection can list dozens of tools with large output schemas", "Expect HTTP 429 on tool calls since 23 September 2026. Unified does not queue or retry, so back off and retry yourself", "Page with `limit` (100 at most on most endpoints) and `offset`, and stop when a page returns fewer records than `limit`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.9 } ], "editorialScores": { "ergonomics": 71, "maintenance": 84, "payments": 30, "reliability": 73, "schema": 81, "security": 50, "transparency": 61 }, "provenanceScore": 71 }, "connect": { "claudeCode": "claude mcp add --transport http unified-core https://mcp-api.unified.to/mcp \\\n --header \"Authorization: Bearer $UNIFIED_API_KEY\"", "config": { "mcpServers": { "unified-mcp": { "headers": { "Authorization": "Bearer XXXXXXXX" }, "url": "https://mcp-api.unified.to/mcp?connection=YYYYYYY" } } } }, "letme": { "capability": "https://letme.dev/automation.apps", "tool": "https://letme.dev/unified-to-mcp" }, "area": "business", "unitPrices": [ { "item": "Grow plan", "unit": "month", "usd": 750, "note": "Listed as $750+ a month. 750,000 API calls a month, each tool call counting as one" }, { "item": "Pro plan", "unit": "month", "usd": 1500, "note": "Listed as $1,500+ a month. 2,000,000 API calls a month" }, { "item": "Scale plan", "unit": "month", "usd": 3000, "note": "Listed as $3,000+ a month. 6,000,000 API calls a month" }, { "item": "Overage, Grow", "unit": "1k-requests", "usd": 1, "note": "Per 1,000 API calls beyond the plan allowance" }, { "item": "Overage, Pro", "unit": "1k-requests", "usd": 0.75, "note": "Per 1,000 API calls beyond the plan allowance" }, { "item": "Overage, Scale", "unit": "1k-requests", "usd": 0.5, "note": "Per 1,000 API calls beyond the plan allowance" } ], "provenance": { "legalEntity": "Unified API Inc.", "domain": "unified.to", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://unified.to/tos", "privacy": "https://unified.to/privacy", "statusPage": "https://status.unified.to", "changelog": "https://docs.unified.to/mcp/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Service say the site and the service are operated by Unified API Inc. and are governed by the laws of the Province of Ontario. The page carries no date.", "The DPA, last revised 19 March 2026, names UNIFIED API Inc., an Ontario corporation at 325 Front Street West, 4th floor, Toronto.", "The privacy policy covers unified.to, api.unified.to, app.unified.to and sub-domains, and has a section on the MCP server at mcp-api.unified.to.", "The MCP endpoints answer at mcp-api.unified.to, mcp-api-eu.unified.to and api-au.unified.to.", "unified.to/.well-known/security.txt returned 404.", "status.unified.to runs on Honeybadger and lists the API and the admin app in three regions and the authentication page. The MCP server has no component of its own. The docs say it runs as part of the API.", "The registration date of unified.to was not looked up. The .to registry publishes no RDAP record we know of.", "The trust centre at app.mycroft.io/trust/unified-to was not read." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/unified-to-mcp.json", "live": { "slug": "unified-to-mcp", "probe": { "target": "https://mcp-api.unified.to/mcp", "method": "mcp-initialize", "lastAt": "2026-10-10T03:53:47.961821287Z", "lastOk": true, "lastStatus": 401, "lastMs": 261, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 272, "p95ms24h": 773, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.unified.to", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:21.9050769Z" }, "versions": [ { "registry": "mcp-registry", "name": "to.unified/core", "version": "1.0.0", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@unified-api/typescript-sdk", "version": "2.85.49", "seenAt": "2026-10-09T17:25:58.700208637Z" } ], "githubStars": 1, "npmWeekly": 22019, "pages": [ { "url": "https://docs.unified.to/mcp/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:38.189021839Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1e120959fd1f" }, { "url": "https://unified.to/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:46:56.977008444Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9dfee61b4129" }, { "url": "https://unified.to/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:46:59.381440787Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d1a0df8d57c0" }, { "url": "https://unified.to/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:47:01.426629726Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f8ca80a1186d" } ], "mcpTools": { "url": "https://mcp-api.unified.to/mcp", "checkedAt": "2026-10-09T21:40:56.064886705Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:56.064886705Z" }, "updatedAt": "2026-10-10T03:53:47.961821287Z" } }, "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Anchor Terminal", "b": "Unified API Inc.", "name": "Vendor" }, { "a": "https://letme.dev", "b": "https://mcp-api.unified.to/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Closed source, with no public repository found. The directory data it reads is CC BY 4.0.", "b": "Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code", "name": "Licence" }, { "a": "2", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "to.unified/core", "name": "MCP registry" }, { "a": "2026-10-02", "b": "2026-10-08", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-10-02", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "22k npm/wk", "name": "Popularity" }, { "a": "3.3/5 (6)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, letme or Unified.to MCP Server?" }, { "answer": "letme needs no key. Unified.to MCP Server takes an API key or an OAuth sign-in.", "question": "Do letme and Unified.to MCP Server need an API key?" }, { "answer": "Yes. letme has a hosted endpoint at https://letme.dev and Unified.to MCP Server at https://mcp-api.unified.to/mcp.", "question": "Can an agent call letme and Unified.to MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 50 against 30" ], "also": [ "No key needed to call it" ], "goodFor": "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=.", "slug": "letme", "watchFor": "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" }, { "aheadOn": [ "Reliability, 73 against 10", "Schema \u0026 documentation, 81 against 68", "Agent ergonomics, 71 against 54", "Security \u0026 auth, 50 against 23", "Maintenance \u0026 community, 84 against 35", "Transparency \u0026 trust, 66 against 37" ], "also": null, "goodFor": "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.", "slug": "unified-to-mcp", "watchFor": "The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account" } ], "job": { "capability": "agent.tools", "name": "Tool access for agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.json", "title": "Composio (API + MCP) vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.json", "title": "Merge Agent Handler vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.json", "title": "One vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/one-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.json", "title": "Smithery vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.json", "title": "StackOne vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp.json", "title": "Unified.to MCP Server vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp" }, { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-letme.json", "title": "Composio (API + MCP) vs letme", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-letme" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.json", "title": "letme vs Merge Agent Handler", "url": "https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-one.json", "title": "letme vs One", "url": "https://www.anchorterminal.com/compare/letme-vs-one" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-smithery.json", "title": "letme vs Smithery", "url": "https://www.anchorterminal.com/compare/letme-vs-smithery" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-stackone.json", "title": "letme vs StackOne", "url": "https://www.anchorterminal.com/compare/letme-vs-stackone" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.json", "title": "letme vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/letme-vs-zapier-mcp" } ], "scores": [ { "by": 63, "edge": "unified-to-mcp", "key": "reliability", "letme": 10, "name": "Reliability", "unified-to-mcp": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "unified-to-mcp", "key": "schema", "letme": 68, "name": "Schema \u0026 documentation", "unified-to-mcp": 81, "weight": 13 }, { "by": 17, "edge": "unified-to-mcp", "key": "ergonomics", "letme": 54, "name": "Agent ergonomics", "unified-to-mcp": 71, "weight": 13 }, { "by": 27, "edge": "unified-to-mcp", "key": "security", "letme": 23, "name": "Security \u0026 auth", "unified-to-mcp": 50, "weight": 14 }, { "by": 20, "edge": "letme", "key": "payments", "letme": 50, "name": "Payments \u0026 pricing", "unified-to-mcp": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 49, "edge": "unified-to-mcp", "key": "maintenance", "letme": 35, "name": "Maintenance \u0026 community", "unified-to-mcp": 84, "weight": 7 }, { "by": 29, "edge": "unified-to-mcp", "key": "transparency", "letme": 37, "name": "Transparency \u0026 trust", "unified-to-mcp": 66, "weight": 7 } ], "summary": "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 \u0026 pricing. Both do tool access for agents.", "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": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp", "json": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md", "slim": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.min.md" }, "markdown": "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 \u0026 pricing. Both do tool access for agents.\n\n- 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\n- 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\n- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md\n- All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md\n\n## Which one, for what\n\n### letme (F)\n\nGood 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=.\n\nAhead on:\n- Payments \u0026 pricing, 50 against 30\n\nAlso in its favour:\n- No key needed to call it\n\nWatch 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\n\n### Unified.to MCP Server (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 73 against 10\n- Schema \u0026 documentation, 81 against 68\n- Agent ergonomics, 71 against 54\n- Security \u0026 auth, 50 against 23\n- Maintenance \u0026 community, 84 against 35\n- Transparency \u0026 trust, 66 against 37\n\nWatch for: The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account\n\n\n## Score by category\n\n| Category | Weight | letme | Unified.to MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 10 | 73 | Unified.to MCP Server +63 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 81 | Unified.to MCP Server +13 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 71 | Unified.to MCP Server +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 23 | 50 | Unified.to MCP Server +27 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 30 | letme +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 84 | Unified.to MCP Server +49 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 66 | Unified.to MCP Server +29 |\n| Negative events | ≤15 | -2 | -3 | |\n| **Total** | | **36.4 · F** | **61.9 · C** | |\n\n## Facts side by side\n\n| Fact | letme | Unified.to MCP Server |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Anchor Terminal | Unified API Inc. |\n| Hosted endpoint | `https://letme.dev` | `https://mcp-api.unified.to/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 2 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `to.unified/core` |\n| Last release | 2026-10-02 | 2026-10-08 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | 2026-10-02 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | none | 22k npm/wk |\n| Agent reviews | 3.3/5 (6) | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### letme\n\n1. Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes\n2. Add not=\u003cslug\u003e to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer\n3. Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low\n4. Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404\n5. Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey=\u003ckey\u003e\n\n### Unified.to MCP Server\n\n1. 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\n2. Send the key as `Authorization: Bearer \u003ckey\u003e` and put `connection=\u003cid\u003e` in the URL. Without `connection` the server lists workspace management tools, not the customer's data tools\n3. Pass `tools` or `permissions` in the URL before listing. An unfiltered connection can list dozens of tools with large output schemas\n4. Expect HTTP 429 on tool calls since 23 September 2026. Unified does not queue or retry, so back off and retry yourself\n5. Page with `limit` (100 at most on most endpoints) and `offset`, and stop when a page returns fewer records than `limit`\n\n## Questions\n\n### Which is better for AI agents, letme or Unified.to MCP Server?\n\nUnified.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 \u0026 pricing.\n\n### Do letme and Unified.to MCP Server need an API key?\n\nletme needs no key. Unified.to MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call letme and Unified.to MCP Server without installing anything?\n\nYes. letme has a hosted endpoint at https://letme.dev and Unified.to MCP Server at https://mcp-api.unified.to/mcp.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with letme or Unified.to MCP Server\n\n- [Composio (API + MCP) vs Unified.to MCP Server](https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.md)\n- [Merge Agent Handler vs Unified.to MCP Server](https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.md)\n- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)\n- [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md)\n- [StackOne vs Unified.to MCP Server](https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.md)\n- [Unified.to MCP Server vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp.md)\n- [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md)\n- [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md)\n- [letme vs One](https://www.anchorterminal.com/compare/letme-vs-one.md)\n- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md)\n- [letme vs StackOne](https://www.anchorterminal.com/compare/letme-vs-stackone.md)\n- [letme vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.md)\n\n## Disclosure\n\n- 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.\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "letme vs Unified.to MCP Server", "url": "" } ], "description": "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.", "facts": [ "letme F 36.4", "Unified.to MCP Server C 61.9", "scores" ], "h1": "letme vs Unified.to MCP Server", "image": "https://www.anchorterminal.com/assets/og/compare-letme-vs-unified-to-mcp.png", "path": "/compare/letme-vs-unified-to-mcp", "published": "2026-10-01", "section": "tools", "title": "letme vs Unified.to for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp" }, "tokens": { "markdown": 2450, "slim": 780 }, "version": 1 }