{ "data": { "a": { "slug": "smithery", "name": "Smithery", "vendor": "Smithery (Arcade.dev)", "vendorUrl": "https://smithery.ai", "kind": "http-api", "category": "aggregator", "summary": "Smithery is a hosted registry and connection service for MCP servers, part of Arcade.dev since August 2026. Agents search the registry, create connections and call tools through a REST API, a per-namespace MCP endpoint, a TypeScript client or a CLI.", "url": "https://www.anchorterminal.com/tools/smithery", "markdownUrl": "https://www.anchorterminal.com/tools/smithery.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/smithery.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/smithery.json", "repo": "https://github.com/smithery-ai/cli", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.smithery.ai", "packages": [ { "registry": "npm", "name": "@smithery/api" }, { "registry": "npm", "name": "smithery" } ], "auth": "mixed", "authNotes": "A person signs in at smithery.ai and creates an API key, which has full access to the namespace and is sent as a Bearer token. `POST /tokens` mints service tokens limited by namespace, resource (connections, servers, namespaces, skills), operation (read, write, execute) and connection metadata, with a default lifetime of one hour and a maximum of 24. Organisation admins can create, list and revoke team API keys. The CLI signs in with OAuth in a browser. Upstream services are authorised by each end user on a hosted setup page, and Smithery stores and refreshes those credentials. Token Scoping is marked preview.", "pricing": "freemium", "pricingNotes": "Prices were not established. smithery.ai/pricing is drawn by script and showed our reader only the navigation. Arcade's announcement of 5 August 2026 says people can sign up for free. Whether a card is needed, what a paid plan costs and whether tool calls are metered were not read (checked 2026-10-09).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI file or the CLI source. The pricing page is drawn by script and was not read (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 840, "npmWeekly": 2729, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://smithery.ai/docs", "llmsTxt": "https://smithery.ai/docs/llms.txt", "openapi": "https://smithery.ai/docs/openapi.json", "capabilities": [ "automation.apps", "automation.auth", "automation.actions", "agent.tools", "automation.webhooks" ], "tags": [ "hosted", "mcp", "registry", "freemium", "api-key", "oauth", "openapi", "llms-txt", "typescript", "cli", "status-page", "closed-source" ], "lastRelease": "2026-07-20", "graded": true, "anchor": { "graded": true, "score": 50.7, "grade": "D", "agentReady": false, "rank": 766, "ranked": true, "rankOf": 950, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 43, "payments": 10, "reliability": 60, "schema": 76, "security": 50, "transparency": 46 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "22 May 2026. CLI release 1.1.1 removed the `smithery skill` subcommand, and on 9 October 2026 the CLI docs page and the repository README still tell users to run `smithery skill search` and `smithery skill add`. A stale claim in the docs, so 2 points (https://github.com/smithery-ai/cli/blob/main/CHANGELOG.md, https://smithery.ai/docs/concepts/cli.md)." ], "verdict": "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.", "bestFor": "A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.", "strengths": [ "Service tokens are scoped by namespace, resource, operation (read, write, execute) and connection metadata, expire within 24 hours and can be narrowed further", "An OpenAPI 3.1 file with 55 operations, `/docs/llms.txt` and a Markdown twin of every docs page", "Connections report `auth_required` or `input_required` with a hosted `setupUrl` and the list of missing fields", "Stored credentials are write-only per the docs, and the credential layer, agent.pw, is published under MIT", "The status page shows 100 per cent uptime over 90 days for the site, the API and the gateway" ], "weaknesses": [ "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", "The privacy notice links a Data Policy at `/docs/use/data-policy`, which answers 404", "No rate limits, 429 response or SLA appear in the docs or the API description", "The CLI repository has had no commit since 31 May 2026 and the API client's last release is 0.68.0 of 20 July 2026", "The CLI docs and README still list `smithery skill` commands that release 1.1.1 removed on 22 May 2026", "Token Scoping and the typed SDKs are marked preview, with breaking changes possible without notice" ], "agentNotes": [ "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", "Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool", "On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId`", "Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories`", "Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.7 } ], "editorialScores": { "ergonomics": 65, "maintenance": 43, "payments": 10, "reliability": 60, "schema": 76, "security": 50, "transparency": 27 }, "provenanceScore": 65 }, "connect": { "install": "npm install -g smithery@latest", "http": "curl -X PUT \"https://smithery.run/my-app/my-browserbase\" \\\n -H \"Authorization: Bearer $SMITHERY_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"mcpUrl\": \"https://mcp.browserbase.com/mcp\"}'" }, "letme": { "capability": "https://letme.dev/automation.apps", "tool": "https://letme.dev/smithery" }, "area": "business", "provenance": { "legalEntity": "Clavia, Inc. (doing business as Smithery)", "domain": "smithery.ai", "domainRegistered": "2024-12-10", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://smithery.ai/privacy", "statusPage": "https://status.smithery.ai", "changelog": "https://github.com/smithery-ai/typescript-api/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Smithery Privacy Notice, last updated 20 June 2025, names Clavia, Inc. doing business as Smithery and covers the Smithery platform and the smithery.ai website. It predates the acquisition and does not name Arcade.", "No terms of service were found. The home page, the pricing page, the about page and the docs link only the privacy notice, so `terms` is left out.", "The privacy notice links a Data Policy at https://smithery.ai/docs/use/data-policy, which answered 404 on 9 October 2026.", "Arcade.dev announced the acquisition of Smithery on 5 August 2026. The acquiring company's legal name was not read.", "The management API answers at api.smithery.ai. Connection calls, the namespace MCP endpoint and Uplink use a second domain, smithery.run.", "smithery.ai/.well-known/security.txt answered 404. The client repository's SECURITY.md sends reports about the service to contact@smithery.ai.", "RDAP gives a registration date of 2024-12-10 for smithery.ai, a transfer on 10 September 2026 and Cloudflare as registrar.", "The changelog link is the TypeScript client's. No dated changelog for the hosted service was found." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/smithery.json", "live": { "slug": "smithery", "probe": { "target": "https://api.smithery.ai", "method": "get", "lastAt": "2026-10-10T04:41:04.411145307Z", "lastOk": true, "lastStatus": 404, "lastMs": 179, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 196, "p95ms24h": 322, "samples24h": 133, "samples30d": 133, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 48, "ok": 48 } ] }, "vendorStatus": { "page": "https://status.smithery.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:16.433925119Z" }, "versions": [ { "registry": "github", "name": "smithery-ai/cli", "version": "v1.2.0", "released": "2026-05-31", "seenAt": "2026-10-09T17:20:48.992258676Z" }, { "registry": "npm", "name": "@smithery/api", "version": "0.68.0", "seenAt": "2026-10-09T17:20:46.778269251Z" }, { "registry": "npm", "name": "smithery", "version": "1.2.0", "seenAt": "2026-10-09T17:20:47.691292694Z" } ], "githubStars": 840, "npmWeekly": 2729, "pages": [ { "url": "https://raw.githubusercontent.com/smithery-ai/typescript-api/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:46:07.185814834Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8bd4ab2d180a" }, { "url": "https://smithery.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:45:32.741358495Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4143bed484bd" } ], "updatedAt": "2026-10-10T04:41:04.411145307Z" } }, "answer": "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.", "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-10T04:41:07.722346973Z", "lastOk": true, "lastStatus": 401, "lastMs": 252, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 270, "p95ms24h": 773, "samples24h": 133, "samples30d": 133, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 48, "ok": 48 } ] }, "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-10T04:41:07.722346973Z" } }, "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Smithery (Arcade.dev)", "b": "Unified API Inc.", "name": "Vendor" }, { "a": "https://api.smithery.ai", "b": "https://mcp-api.unified.to/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code", "name": "Licence" }, { "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-07-20", "b": "2026-10-08", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-06-20", "b": "2026-10-02", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "840 stars, 2.7k npm/wk", "b": "22k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, Smithery or Unified.to MCP Server?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Smithery and Unified.to MCP Server need an API key?" }, { "answer": "Yes. Smithery has a hosted endpoint at https://api.smithery.ai and Unified.to MCP Server at https://mcp-api.unified.to/mcp.", "question": "Can an agent call Smithery and Unified.to MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.", "slug": "smithery", "watchFor": "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" }, { "aheadOn": [ "Reliability, 73 against 60", "Schema \u0026 documentation, 81 against 76", "Agent ergonomics, 71 against 65", "Payments \u0026 pricing, 30 against 10", "Maintenance \u0026 community, 84 against 43", "Transparency \u0026 trust, 66 against 46" ], "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": "automation.apps", "name": "App automation" }, "others": [ { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-smithery.json", "title": "Composio (API + MCP) vs Smithery", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-smithery" }, { "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-smithery.json", "title": "Merge Agent Handler vs Smithery", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery" }, { "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-smithery.json", "title": "One vs Smithery", "url": "https://www.anchorterminal.com/compare/one-vs-smithery" }, { "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-stackone.json", "title": "Smithery vs StackOne", "url": "https://www.anchorterminal.com/compare/smithery-vs-stackone" }, { "json": "https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.json", "title": "Smithery vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/smithery-vs-zapier-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/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-unified-to-mcp.json", "title": "letme vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp" } ], "scores": [ { "by": 13, "edge": "unified-to-mcp", "key": "reliability", "name": "Reliability", "smithery": 60, "unified-to-mcp": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "unified-to-mcp", "key": "schema", "name": "Schema \u0026 documentation", "smithery": 76, "unified-to-mcp": 81, "weight": 13 }, { "by": 6, "edge": "unified-to-mcp", "key": "ergonomics", "name": "Agent ergonomics", "smithery": 65, "unified-to-mcp": 71, "weight": 13 }, { "by": 0, "edge": "", "key": "security", "name": "Security \u0026 auth", "smithery": 50, "unified-to-mcp": 50, "weight": 14 }, { "by": 20, "edge": "unified-to-mcp", "key": "payments", "name": "Payments \u0026 pricing", "smithery": 10, "unified-to-mcp": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 41, "edge": "unified-to-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "smithery": 43, "unified-to-mcp": 84, "weight": 7 }, { "by": 20, "edge": "unified-to-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "smithery": 46, "unified-to-mcp": 66, "weight": 7 } ], "summary": "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.", "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": "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/smithery-vs-unified-to-mcp", "json": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md", "slim": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.min.md" }, "markdown": "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.\n\n- 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\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### Smithery (D)\n\nGood for: A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.\n\nWatch 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\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 60\n- Schema \u0026 documentation, 81 against 76\n- Agent ergonomics, 71 against 65\n- Payments \u0026 pricing, 30 against 10\n- Maintenance \u0026 community, 84 against 43\n- Transparency \u0026 trust, 66 against 46\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 | Smithery | Unified.to MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 73 | Unified.to MCP Server +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 76 | 81 | Unified.to MCP Server +5 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 71 | Unified.to MCP Server +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 50 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 30 | Unified.to MCP Server +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 43 | 84 | Unified.to MCP Server +41 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 46 | 66 | Unified.to MCP Server +20 |\n| Negative events | ≤15 | -2 | -3 | |\n| **Total** | | **50.7 · D** | **61.9 · C** | |\n\n## Facts side by side\n\n| Fact | Smithery | Unified.to MCP Server |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Smithery (Arcade.dev) | Unified API Inc. |\n| Hosted endpoint | `https://api.smithery.ai` | `https://mcp-api.unified.to/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `to.unified/core` |\n| Last release | 2026-07-20 | 2026-10-08 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | 2025-06-20 | 2026-10-02 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | yes |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 840 stars, 2.7k npm/wk | 22k npm/wk |\n\n## Verdicts\n\n**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.\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### Smithery\n\n1. 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\n2. Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool\n3. On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId`\n4. Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories`\n5. Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them\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, Smithery or Unified.to MCP Server?\n\nUnified.to MCP Server scores 61.9 (C) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories.\n\n### Do Smithery and Unified.to MCP Server need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Smithery and Unified.to MCP Server without installing anything?\n\nYes. Smithery has a hosted endpoint at https://api.smithery.ai 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/smithery-vs-unified-to-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.min.md\n- 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`\n- 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\n\n## Other comparisons with Smithery or Unified.to MCP Server\n\n- [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md)\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 Smithery](https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.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 Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md)\n- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)\n- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)\n- [Smithery vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/smithery-vs-zapier-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- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md)\n- [letme vs Unified.to MCP Server](https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md)\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": "Smithery vs Unified.to MCP Server", "url": "" } ], "description": "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.", "facts": [ "Smithery D 50.7", "Unified.to MCP Server C 61.9", "scores" ], "h1": "Smithery vs Unified.to MCP Server", "image": "https://www.anchorterminal.com/assets/og/compare-smithery-vs-unified-to-mcp.png", "path": "/compare/smithery-vs-unified-to-mcp", "published": "2026-10-01", "section": "tools", "title": "Smithery vs Unified.to for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp" }, "tokens": { "markdown": 2250, "slim": 730 }, "version": 1 }