{ "data": { "a": { "slug": "one", "name": "One", "vendor": "One Systems, Inc.", "vendorUrl": "https://www.withone.ai", "kind": "mcp", "category": "aggregator", "summary": "One is a hosted MCP server and CLI from One Systems, Inc. (formerly Pica) that lets AI agents find and run actions in a user's connected apps, with credentials held by One and access scoped per connection.", "url": "https://www.anchorterminal.com/tools/one", "markdownUrl": "https://www.anchorterminal.com/tools/one.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/one.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/one.json", "repo": "https://github.com/withoneai/mcp", "license": "Proprietary hosted service under One's Terms of Service. The local MCP server package `@withone/mcp` is MIT. The CLI package `@withone/cli` has no licence field or licence file. The knowledge base is under the One Knowledge Commons Licence v1.0, which is not an OSI licence", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp.withone.ai/mcp", "packages": [ { "registry": "npm", "name": "@withone/mcp" }, { "registry": "npm", "name": "@withone/cli" } ], "auth": "mixed", "authNotes": "Self-serve. The remote server uses OAuth 2.1 authorisation code with PKCE (S256). The client registers itself at `https://mcp.withone.ai/oauth/register` as a public client, a person signs in to One in a browser, and the consent screen picks the account, Production or Sandbox, and an access level per connection. Scopes are `connections:read` and `connections:write` under `user:`, `org:` and `project:`, and a client that asks for none gets all six. Access tokens last one hour, with a 30-day refresh token when the client registers that grant. The local package and the REST API take an API key in the `x-one-secret` header, and a key created through the CLI's browser sign-in carries the same per-connection limits. Third-party accounts are connected in the dashboard or with `one add \u003cplatform\u003e`, and One stores those credentials.", "pricing": "freemium", "pricingNotes": "Free is $0 with 1M requests a month, 20 requests a minute, one organisation and one project. Starter is $29 a month at 100 requests a minute and Pro is $199 a month at 500, each with 1M requests a month. Enterprise is priced on contract. Requests over the limit answer 429 and there is no overage charge. A cloud agent on a dedicated server is $40 a month on any plan. The pricing page doesn't say whether sign-up needs a card. The API authentication page says both environments include unlimited API calls, which doesn't match the 1M a month on the pricing page (https://www.withone.ai/pricing, checked 2026-10-09).", "priceSummary": "$29 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the MCP docs, the pricing page or the OpenAPI file. The API's 402 responses are described as a plan quota, not a payment protocol (checked 2026-10-09).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 11, "npmWeekly": 681, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.withone.ai/docs/mcp", "llmsTxt": "https://www.withone.ai/llms.txt", "openapi": "https://www.withone.ai/openapi.json", "registryName": "ai.withone/mcp", "capabilities": [ "automation.apps", "automation.auth", "automation.actions", "agent.tools", "auth.audit" ], "tags": [ "hosted", "mcp", "freemium", "free-tier", "oauth", "openapi", "llms-txt", "cli", "typescript", "status-page", "mcp-registry" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 66.6, "grade": "B", "agentReady": false, "rank": 282, "ranked": true, "rankOf": 950, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 86, "payments": 30, "reliability": 82, "schema": 77, "security": 69, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "Between 13 July and 30 September 2026 the remote MCP server's tools changed from four to three. The changelog entry of 13 July 2026 says the remote server has the same four tools as the local one, and the local package's 2.0.0 commit of 30 September 2026 removes `search_one_platform_actions` and `get_one_action_knowledge` for `find_one_actions`, which it calls the tool the remote server already serves. The site's changelog has no entry for the change. The local package marked it as a major version. Three points off (https://www.withone.ai/changelog, https://github.com/withoneai/mcp)." ], "verdict": "One's remote MCP server has three tools, OAuth 2.1 sign-in with PKCE and a consent screen that sets read only, read and write, full or per-action access for each connection. A person must sign in through a browser, the SOC 2 audit is unfinished, and the site's changelog stops at 13 July 2026.", "bestFor": "A person or small team that wants one MCP entry with a small tool footprint across many SaaS accounts, with access set per connection and a free plan.", "strengths": [ "The remote server has three tools whatever the number of connections, and `find_one_actions` returns large documents as a digest with sections loaded on request", "The consent screen sets Full access, Read \u0026 write, Read only or a ticked list of actions per connection, and One enforces the grant on every call", "Access tokens last one hour, and changing or revoking a grant in the dashboard applies on the agent's next call", "Every plan, Free included, lists the same platforms and controls. Plans differ by requests per minute (20, 100, 500), organisations and projects, with no overage charge", "The server is in the official MCP registry as `ai.withone/mcp`, and the CLI had 14 npm releases between 25 August and 6 October 2026" ], "weaknesses": [ "The remote server's tools changed from four to three by 30 September 2026, and the site's changelog, last dated 13 July 2026, has no entry for it", "The home and security pages say nothing from a call is stored. The privacy policy says request logs may include integration payloads, kept 14 to 90 days by default", "The SOC 2 audit is described as in progress, `/.well-known/security.txt` returned 404, and no bug bounty or published advisories were found", "`execute_one_action` takes a free-form `data` body and returns the upstream response whole. No control on response size was found", "The Data Processing Agreement is available only on request, and no deprecation policy was found" ], "agentNotes": [ "Call `list_one_integrations` first and read each connection's `access` field. When the policy is `actions`, run those ids directly without calling `find_one_actions`", "Send every operation a task needs in one `find_one_actions` call, up to 10 `requests`, each a platform and a short intent with no IDs, names or message text", "When a document comes back as a digest, call `find_one_actions` again with `load` and a `section` name. Don't guess parameters the digest left out", "After a timeout on `execute_one_action`, check whether the write took effect before sending it again. No idempotency key is documented", "A 403 for a call outside the grant won't succeed on retry. Ask the user to widen the grant in the dashboard or reconnect" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.6 } ], "editorialScores": { "ergonomics": 73, "maintenance": 86, "payments": 30, "reliability": 82, "schema": 77, "security": 69, "transparency": 54 }, "provenanceScore": 72 }, "connect": { "install": "npm install -g @withone/cli \u0026\u0026 one init", "claudeCode": "claude mcp add --transport http one https://mcp.withone.ai/mcp", "config": { "mcpServers": { "one": { "type": "http", "url": "https://mcp.withone.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/automation.apps", "tool": "https://letme.dev/one" }, "area": "business", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 29, "note": "1M requests a month, 100 requests a minute, 20 organisations and 20 projects" }, { "item": "Pro plan", "unit": "month", "usd": 199, "note": "1M requests a month, 500 requests a minute, 100 organisations and 100 projects" }, { "item": "Cloud agent on a dedicated server", "unit": "month", "usd": 40, "note": "Per agent, added to any plan" } ], "provenance": { "legalEntity": "One Systems, Inc.", "domain": "withone.ai", "domainRegistered": "2026-01-22", "endpointOnVendorDomain": true, "terms": "https://www.withone.ai/terms", "privacy": "https://www.withone.ai/privacy", "statusPage": "https://status.withone.ai", "changelog": "https://www.withone.ai/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Service, last updated 6 March 2026, name One Systems, Inc. of San Francisco and cover the website, platform, APIs and SDKs under California law. No state of incorporation is given.", "The privacy policy, last updated 22 July 2026, governs account and usage data. For data passing through connected apps it points to a Data Processing Agreement that is available on request and not published.", "RDAP gives a registration date of 2026-01-22 for withone.ai. The product traded as Pica on picaos.com before 25 March 2026.", "www.withone.ai/.well-known/security.txt returned 404. The security page gives security@withone.ai for disclosure.", "status.withone.ai is a Better Stack page created in March 2025. We did not find a link to it on the vendor pages we read.", "The MCP server answers at mcp.withone.ai and the REST API at api.withone.ai." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/one.json", "live": { "slug": "one", "probe": { "target": "https://mcp.withone.ai/mcp", "method": "mcp-initialize", "lastAt": "2026-10-10T04:40:57.9688527Z", "lastOk": true, "lastStatus": 401, "lastMs": 162, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 165, "p95ms24h": 260, "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.withone.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:54.124632614Z" }, "versions": [ { "registry": "github", "name": "withoneai/mcp", "version": "2.0.0", "released": "2026-09-30", "seenAt": "2026-10-09T17:09:32.922283746Z" }, { "registry": "mcp-registry", "name": "ai.withone/mcp", "version": "2.0.0", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@withone/cli", "version": "2.6.0", "seenAt": "2026-10-09T17:09:31.577452422Z" }, { "registry": "npm", "name": "@withone/mcp", "version": "2.0.0", "seenAt": "2026-10-09T17:09:30.715852547Z" } ], "githubStars": 11, "npmWeekly": 681, "pages": [ { "url": "https://www.withone.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:55:40.085470155Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7efc2d05b2eb" }, { "url": "https://www.withone.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:55:42.392440467Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "991db7361edb" }, { "url": "https://www.withone.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:55:44.31680918Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cf8afffd8c96" }, { "url": "https://www.withone.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:55:46.353715719Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6ed34b101d9b" } ], "mcpTools": { "url": "https://mcp.withone.ai/mcp", "checkedAt": "2026-10-09T21:40:46.685955698Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:46.685955698Z" }, "updatedAt": "2026-10-10T04:40:57.9688527Z" } }, "answer": "One scores 66.6 (B) on agent readiness against Smithery's 50.7 (D), and leads in every scored category.", "b": { "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" } }, "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "One Systems, Inc.", "b": "Smithery (Arcade.dev)", "name": "Vendor" }, { "a": "https://mcp.withone.ai/mcp", "b": "https://api.smithery.ai", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, stdio", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under One's Terms of Service. The local MCP server package `@withone/mcp` is MIT. The CLI package `@withone/cli` has no licence field or licence file. The knowledge base is under the One Knowledge Commons Licence v1.0, which is not an OSI licence", "b": "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", "name": "Licence" }, { "a": "3", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.withone/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-07-20", "name": "Last release" }, { "a": "2026-03-06", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-07-22", "b": "2025-06-20", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "11 stars, 681 npm/wk", "b": "840 stars, 2.7k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "One scores 66.6 (B) on agent readiness against Smithery's 50.7 (D), and leads in every scored category.", "question": "Which is better for AI agents, One or Smithery?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do One and Smithery need an API key?" }, { "answer": "Yes. One has a hosted endpoint at https://mcp.withone.ai/mcp and Smithery at https://api.smithery.ai.", "question": "Can an agent call One and Smithery without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 82 against 60", "Agent ergonomics, 73 against 65", "Security \u0026 auth, 69 against 50", "Payments \u0026 pricing, 30 against 10", "Maintenance \u0026 community, 86 against 43", "Transparency \u0026 trust, 63 against 46" ], "also": [ "Runs on your own machine" ], "goodFor": "A person or small team that wants one MCP entry with a small tool footprint across many SaaS accounts, with access set per connection and a free plan.", "slug": "one", "watchFor": "The remote server's tools changed from four to three by 30 September 2026, and the site's changelog, last dated 13 July 2026, has no entry for it" }, { "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" } ], "job": { "capability": "automation.apps", "name": "App automation" }, "others": [ { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-one.json", "title": "Composio (API + MCP) vs One", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-one" }, { "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/merge-agent-handler-vs-one.json", "title": "Merge Agent Handler vs One", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-one" }, { "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/one-vs-stackone.json", "title": "One vs StackOne", "url": "https://www.anchorterminal.com/compare/one-vs-stackone" }, { "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/one-vs-zapier-mcp.json", "title": "One vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/one-vs-zapier-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-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/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/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" } ], "scores": [ { "by": 22, "edge": "one", "key": "reliability", "name": "Reliability", "one": 82, "smithery": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "one", "key": "schema", "name": "Schema \u0026 documentation", "one": 77, "smithery": 76, "weight": 13 }, { "by": 8, "edge": "one", "key": "ergonomics", "name": "Agent ergonomics", "one": 73, "smithery": 65, "weight": 13 }, { "by": 19, "edge": "one", "key": "security", "name": "Security \u0026 auth", "one": 69, "smithery": 50, "weight": 14 }, { "by": 20, "edge": "one", "key": "payments", "name": "Payments \u0026 pricing", "one": 30, "smithery": 10, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 43, "edge": "one", "key": "maintenance", "name": "Maintenance \u0026 community", "one": 86, "smithery": 43, "weight": 7 }, { "by": 17, "edge": "one", "key": "transparency", "name": "Transparency \u0026 trust", "one": 63, "smithery": 46, "weight": 7 } ], "summary": "One scores 66.6 (B) on agent readiness against Smithery's 50.7 (D), and leads in every scored category. Both do app automation.", "verdicts": { "one": "One's remote MCP server has three tools, OAuth 2.1 sign-in with PKCE and a consent screen that sets read only, read and write, full or per-action access for each connection. A person must sign in through a browser, the SOC 2 audit is unfinished, and the site's changelog stops at 13 July 2026.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/one-vs-smithery", "json": "https://www.anchorterminal.com/compare/one-vs-smithery.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/one-vs-smithery.md", "slim": "https://www.anchorterminal.com/compare/one-vs-smithery.min.md" }, "markdown": "One scores 66.6 (B) on agent readiness against Smithery's 50.7 (D), and leads in every scored category. Both do app automation.\n\n- One: grade B, 66.6/100, rank #282 of 950. Markdown https://www.anchorterminal.com/tools/one.md · JSON https://www.anchorterminal.com/api/v1/tools/one.json\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- 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### One (B)\n\nGood for: A person or small team that wants one MCP entry with a small tool footprint across many SaaS accounts, with access set per connection and a free plan.\n\nAhead on:\n- Reliability, 82 against 60\n- Agent ergonomics, 73 against 65\n- Security \u0026 auth, 69 against 50\n- Payments \u0026 pricing, 30 against 10\n- Maintenance \u0026 community, 86 against 43\n- Transparency \u0026 trust, 63 against 46\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: The remote server's tools changed from four to three by 30 September 2026, and the site's changelog, last dated 13 July 2026, has no entry for it\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\n## Score by category\n\n| Category | Weight | One | Smithery | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 82 | 60 | One +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 76 | One +1 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 65 | One +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 50 | One +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 10 | One +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 86 | 43 | One +43 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 46 | One +17 |\n| Negative events | ≤15 | -3 | -2 | |\n| **Total** | | **66.6 · B** | **50.7 · D** | |\n\n## Facts side by side\n\n| Fact | One | Smithery |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | One Systems, Inc. | Smithery (Arcade.dev) |\n| Hosted endpoint | `https://mcp.withone.ai/mcp` | `https://api.smithery.ai` |\n| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary hosted service under One's Terms of Service. The local MCP server package `@withone/mcp` is MIT. The CLI package `@withone/cli` has no licence field or licence file. The knowledge base is under the One Knowledge Commons Licence v1.0, which is not an OSI 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 |\n| Tools exposed | 3 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.withone/mcp` | not listed |\n| Last release | 2026-10-06 | 2026-07-20 |\n| Terms last updated | 2026-03-06 | no document linked |\n| Privacy policy last updated | 2026-07-22 | 2025-06-20 |\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 | 11 stars, 681 npm/wk | 840 stars, 2.7k npm/wk |\n\n## Verdicts\n\n**One.** One's remote MCP server has three tools, OAuth 2.1 sign-in with PKCE and a consent screen that sets read only, read and write, full or per-action access for each connection. A person must sign in through a browser, the SOC 2 audit is unfinished, and the site's changelog stops at 13 July 2026.\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## Before you call either\n\n### One\n\n1. Call `list_one_integrations` first and read each connection's `access` field. When the policy is `actions`, run those ids directly without calling `find_one_actions`\n2. Send every operation a task needs in one `find_one_actions` call, up to 10 `requests`, each a platform and a short intent with no IDs, names or message text\n3. When a document comes back as a digest, call `find_one_actions` again with `load` and a `section` name. Don't guess parameters the digest left out\n4. After a timeout on `execute_one_action`, check whether the write took effect before sending it again. No idempotency key is documented\n5. A 403 for a call outside the grant won't succeed on retry. Ask the user to widen the grant in the dashboard or reconnect\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## Questions\n\n### Which is better for AI agents, One or Smithery?\n\nOne scores 66.6 (B) on agent readiness against Smithery's 50.7 (D), and leads in every scored category.\n\n### Do One and Smithery need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call One and Smithery without installing anything?\n\nYes. One has a hosted endpoint at https://mcp.withone.ai/mcp and Smithery at https://api.smithery.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/one-vs-smithery.json, and with the fewest tokens: https://www.anchorterminal.com/compare/one-vs-smithery.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"one\", \"b\": \"smithery\"}`. From a terminal: `anchor compare one smithery`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/one.json and https://www.anchorterminal.com/api/v1/tools/smithery.json\n\n## Other comparisons with One or Smithery\n\n- [Composio (API + MCP) vs One](https://www.anchorterminal.com/compare/composio-rube-vs-one.md)\n- [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md)\n- [Merge Agent Handler vs One](https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.md)\n- [Merge Agent Handler vs Smithery](https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.md)\n- [One vs StackOne](https://www.anchorterminal.com/compare/one-vs-stackone.md)\n- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)\n- [One vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/one-vs-zapier-mcp.md)\n- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)\n- [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md)\n- [Smithery vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.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", "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": "One vs Smithery", "url": "" } ], "description": "One scores 66.6 (B) to Smithery's 50.7 (D) for app automation. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "One B 66.6", "Smithery D 50.7", "scores" ], "h1": "One vs Smithery", "image": "https://www.anchorterminal.com/assets/og/compare-one-vs-smithery.png", "path": "/compare/one-vs-smithery", "published": "2026-10-01", "section": "tools", "title": "One vs Smithery for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/one-vs-smithery" }, "tokens": { "markdown": 2200, "slim": 780 }, "version": 1 }