# MCP Gateway vs Smithery > MCP Gateway scores 71 (BB) to Smithery's 51 (D) for tool access for agents. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-smithery - Markdown: https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-smithery.md (~5,200 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-02 MCP Gateway scores 71 (BB) on agent readiness against Smithery's 51 (D), and leads in 6 of 7 scored categories. Both do tool access for agents. - MCP Gateway: grade BB, 71/100, rank #158 of 1266. Markdown https://www.anchorterminal.com/tools/mcp-gateway-parkkola.md · JSON https://www.anchorterminal.com/api/v1/tools/mcp-gateway-parkkola.json - Smithery: grade D, 51/100, rank #945 of 1266. Markdown https://www.anchorterminal.com/tools/smithery.md · JSON https://www.anchorterminal.com/api/v1/tools/smithery.json - Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md - All 55 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md ## Which one, for what ### MCP Gateway (BB) Good for: One person running many local and remote MCP servers who wants a single local entry with a small tool list, scoped keys and poisoning checks Ahead on: - Reliability, 87 against 60 - Agent ergonomics, 77 against 65 - Security & auth, 80 against 50 - Payments & pricing, 30 against 10 - Maintenance & community, 90 against 43 - Transparency & trust, 60 against 49 Also in its favour: - Agent-ready, a grade of BB or better - Runs on your own machine - Free to start without a card Watch for: The project's own live run found the meta path used 1.2 to 16.1 per cent more input tokens and one extra turn on every task ### Smithery (D) Good for: A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens. Also in its favour: - A hosted endpoint, with nothing to install Watch for: No terms of service are linked from the site, the docs or the footer. The privacy notice of 20 June 2025 is the only legal document found ## Why the edge ### Maintenance & community: MCP Gateway +47 - MCP Gateway (90): 4.0.0-beta.3 on 6 October 2026, 27 days before the check, and commits on main to 26 October (30). 4.0.0-beta.1 and beta.2 on 25 September and beta.3 on 6 October, plus 3.5.1 on 4 September, inside 90 days (20). The newest outside issue (#3953, 19 October) got a maintainer reply the same day and a follow-up on 28 October, four issues are open, and outside pull requests from four contributors were merged, per AUTHORSHIP.md. Closed issues and pull requests couldn't be read (robots.txt), so not sampled further (17 of 25). In the official MCP registry as io.github.MikkoParkkola/mcp-gateway under a GitHub namespace, latest 3.5.1, the current stable release (15). Dependabot merges, cargo audit in CI and current tokio and jsonschema, less 2 because the npm wrapper installs a downloaded binary without checking its checksum (8 of 10). 30 + 20 + 17 + 15 + 8 = 90. - Smithery (43): The newest release found is `@smithery/api` 0.68.0 on 20 July 2026, 81 days before the check. The CLI's last release and last commit are 1.2.0 on 31 May 2026 (20). One release in the last 90 days (0). The CLI repository, now under arcadeai-labs, shows 51 open issues and no push since 31 May. The issues themselves were not read, and a Discord server is linked for support (6). One current official client, in TypeScript (10). Both repositories carry CI workflows, lockfiles and release automation (7). ### Security & auth: MCP Gateway +30 - MCP Gateway (80): Read with the API checklist, as the gateway is the security layer an operator puts in front of agents. Over HTTP, bearer tokens and API keys with per-key glob allow and deny lists, explicit admin keys, OIDC JWT and mTLS, with OAuth 2.1 to backends, per-issuer token storage and per-user isolation that fails closed. Authentication is off by default on the loopback HTTP port, where callers are anonymous non-admins, and a stdio caller is admin (24 of 30). Management tools need an admin credential since 3.5.0, per-key tool scopes give least privilege, and destructive meta-tools ask the human through elicitation, refused on the 2026-07-28 protocol when the client can't ask and allowed after a warning on older clients; the source calls the prompt a courtesy, with the admin requirement as the control (16 of 20). Backend tool descriptions are scanned for poisoning patterns before they reach the agent, capability files can be hash-pinned, and responses pass a pattern-based injection scanner and credential redactor (13 of 15). NDJSON audit log, per-key cost and usage accounting, Prometheus metrics and trace ids (13 of 15). SECURITY.md with private reporting, a 48-hour acknowledgement and a 7-day fix target; two advisories published with credit on 28 August 2026; cargo audit, secret scanning and cosign-signed images in CI; no bug bounty or security.txt, and the OWASP mapping is self-assessed (14 of 20). 24 + 16 + 13 + 13 + 14 = 80. The DNS-rebinding advisory is a negative event below. - Smithery (50): An API key has full namespace access. Service tokens are scoped by namespace, resource, operation and metadata, last 24 hours at most and can be narrowed, and team keys can be revoked. Token Scoping is in preview (26). Read-only and execute-only tokens are documented. No approval step for destructive tools was found (12). Connected servers return third-party content. A registry record carries `security.scanPassed`, and no prompt-injection guidance was found (4). Runtime logs by invocation exist for people who publish a server. No call log for connection users was found (5). The docs say stored credentials are encrypted and write-only. security.txt answered 404, and no certification, bounty or disclosure policy was found beyond a contact address (3). ### Reliability: MCP Gateway +27 - MCP Gateway (87): Local-package reading, as for graphicle and claude-mem, since the owner runs it. Official packages on crates.io (`cargo install mcp-gateway`), a Homebrew tap, release binaries and ghcr.io, with Rust 1.95 and macOS, Linux and Windows builds stated (20). A public CI workflow runs clippy with warnings as errors, the full test suite, fmt, cargo audit, secret scans and Helm smoke tests on pushes and pull requests, and the last eight runs on main passed by 26 October 2026 (25). Four open issues on GitHub on 2 November 2026, one a labelled bug filed by the maintainer, and the newest outside issue was answered the day it was opened. Closed issues couldn't be read (robots.txt), so the record is partial (18 of 25). Keep a Changelog with BREAKING entries and migration notes for 3.0 and 4.0 and an UPGRADING-4.0.md, but 3.3.0, which relicensed the code, has no changelog section, and 4.0.0 is dated 19 September there while only betas exist (9 of 15). Stable is 3.5.1, after two earlier majors; 4.0.0 is in beta (15). 20 + 25 + 18 + 9 + 15 = 87. - Smithery (60): Read with the hosted lines. status.smithery.ai on Better Stack lists the site, the API and the gateway (20). Each shows 100 per cent uptime over 90 days. The page's incident list is a script-drawn tab and was not read, so 25 of 30 (25). No rate limits were found in the docs index or the API description (0). The API description declares no 429. The TypeScript client retries 408, 409, 429 and 5xx twice with backoff, and the `PUT` endpoints are described as idempotent upserts. No retry guidance for tool calls was found (8). No SLA was found (0). The connection API carries no beta label, while Token Scoping and the typed SDKs are marked preview and the client is at 0.68 (7). ### Payments & pricing: MCP Gateway +20 - MCP Gateway (30): Self-hosted rule, scored on the paid option because any company use needs a commercial licence, as gaia and screenpipe (also noncommercial licences) were read. No payment protocol (0). The standard commercial licence is a public flat EUR 500 a month per named project through GitHub Sponsors, plan-only pricing (10). Personal and noncommercial use is free with no card or account, but there is no free route or stated evaluation period for a company (10 of 20). It installs from Homebrew, crates.io or ghcr.io with no sign-up, and an agent with a shell can run the setup wizard, but buying the licence takes a person on GitHub Sponsors, as screenpipe's did (10 of 20). 0 + 10 + 10 + 10 = 30. - Smithery (10): No x402, MPP or L402 (0). The pricing page is drawn by script and was not read, so no price is scored. This is a limit of our reading and not a finding about the vendor (0). Arcade's announcement says sign-up is free. Whether a card is needed was not established, so half marks (10). A person signs in through a browser to get an API key or to log the CLI in (0). ### Agent ergonomics: MCP Gateway +12 - MCP Gateway (77): MCP context cost. Nine to 17 meta-tools, 11 in the default admin set, whatever the number of backends, so 15 for 11 to 30 tools, plus 10 back for Code Mode's two tools, `exposed_meta_tools` and surfaced tools (25). The project's own live run of 4 September 2026 found the meta path used 1.2 to 16.1 per cent more input tokens and one extra turn on every task, which the README states; the context saving is a schema-size saving, so less 5 (20 of 25). `gateway_search_tools` and `gateway_search` take `limit`, `gateway_search` has L0, L1 and L2 detail tiers, `gateway_list_tools` filters by server and role, and backend responses can be shaped with transform chains (17 of 20). Did-you-mean on tool names, LLM-readable output-schema failures, circuit-breaker and disabled status in `gateway_list_servers`, and rate-limited calls excluded from the kill budgets (16 of 20). Meta-tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint; destructive meta-tools ask through elicitation, which the source calls a courtesy rather than a control; an idempotency guard exists per ADR-012 (16 of 20). One required argument for search and two for invoke; Rust only, no SDK applies, and setup takes a wizard and a config file (8 of 15). 20 + 17 + 16 + 16 + 8 = 77. - Smithery (65): Graded as an API. Registry lists take `fields`, the CLI has `tool find` and `tool get`, and one call lists tools across a namespace. The namespace MCP endpoint loads every connection's tools, so context grows with the number of connections (15). `page` and `pageSize` up to 100, `cursor` and `limit` on connections, and metadata filters (16). Errors carry `error` and `message`, and a connection that needs action returns `auth_required` or `input_required` with `setupUrl` and the missing fields (15). Upserts are idempotent and the client retries safely. Tool calls take no idempotency key, and whether upstream MCP annotations are passed through was not established (10). A namespace and connection ID are created when omitted. One official client language, TypeScript, plus the CLI (9). ### Transparency & trust: MCP Gateway +11 - MCP Gateway (60): PolyForm Noncommercial 1.0.0, source-available and not OSI, with affirmative SPDX headers on every first-party file and LICENSES.md, NOTICE.md and COMMERCIAL.md that agree with each other and say what the earlier MIT grants still cover. Read as gaia's PolyForm source was (20 of 30). Self-hosted, so data stays where the owner runs it; secrets go to the OS keychain, files holding them are 0600 on Unix, and SECURITY.md states the Windows gap. There is no privacy statement (20 of 30). Deprecation notices with versions for the MIT 3.0.0 to 3.2.1 releases on crates.io and npm, upgrade guides for 3.0 and 4.0 and a stated support window of the latest release only, but the 3.3.0 relicence has no changelog entry, and AUTHORSHIP.md says the licensing scheme still awaits an IP lawyer's sign-off (9 of 20). No telemetry, analytics or update check found in the source; Prometheus metrics stay local behind a feature flag, and the plugin marketplace host is contacted only by plugin commands. The docs state nothing either way (15 of 20). 20 + 20 + 9 + 15 = 64. - Smithery (49): The editorial half. The hosted service is closed and no terms of service were found. The CLI is AGPL-3.0, the client Apache-2.0 and the credential layer MIT (12). The privacy notice of 20 June 2025 gives no retention periods, says customer content is used to improve products, describes targeted advertising, and links a Data Policy that answers 404. A data processing agreement is available on request (8). Deprecated operations are marked in the API description with their replacements, with no dates and no policy (5). Stripe is the only processor named, and no hosting location or sub-processor list was found (2). ## Score by category | Category | Weight | MCP Gateway | Smithery | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 87 | 60 | MCP Gateway +27 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 75 | 76 | Smithery +1 | | Agent ergonomics | 13% (16.2 this run) | 77 | 65 | MCP Gateway +12 | | Security & auth | 14% (17.5 this run) | 80 | 50 | MCP Gateway +30 | | Payments & pricing | 10% (12.5 this run) | 30 | 10 | MCP Gateway +20 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 90 | 43 | MCP Gateway +47 | | Transparency & trust | 7% (8.8 this run) | 60 | 49 | MCP Gateway +11 | | Negative events | ≤15 | -2 | -2 | | | **Total** | | **71 · BB** | **51 · D** | | ## Facts side by side | Fact | MCP Gateway | Smithery | | --- | --- | --- | | Kind | MCP server | HTTP API | | Vendor | Mikko Parkkola | Smithery (Arcade.dev) | | Hosted endpoint | no (local only) | `https://api.smithery.ai` | | Transports | stdio, Streamable HTTP, SSE (legacy), websocket | HTTP, Streamable HTTP | | Auth | OAuth or key | OAuth or key | | Pricing | Freemium | Freemium | | x402 | no | no | | Licence | PolyForm Noncommercial 1.0.0 (source-available, not OSI) for every first-party file from 4.0.0. Personal and noncommercial use is free; running it in or for a business needs a commercial licence at EUR 500 a month per named project through GitHub Sponsors. 3.0.0 to 3.2.1 shipped as MIT and stay MIT for those copies, and 3.3.x shipped a small MIT core under per-file headers | 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 | | Tools exposed | 11 | none | | Read-only variant documented | no | no | | llms.txt | yes | yes | | MCP registry | `io.github.MikkoParkkola/mcp-gateway` | not listed | | Last release | 2026-10-06 | 2026-07-20 | | Terms last updated | no date given | no document linked | | Privacy policy last updated | no document linked | 2025-06-20 | | Customer content may train models | not found in the text | not read yet | | Terms restrict automated access | not found in the text | not read yet | | Terms restrict benchmarking | not found in the text | not read yet | | Terms or service can change without notice | not found in the text | not read yet | | Arbitration or class-action waiver | not found in the text | not read yet | | Popularity | 65 stars, 49 npm/wk | 840 stars, 2.7k npm/wk | ## How the scores have moved ### MCP Gateway No score change since it was listed. ### Smithery - +0.3 on 27 October 2026: checklist ## Verdicts **MCP Gateway.** A local gateway that puts many MCP servers and REST APIs behind 9 to 17 typed, annotated meta-tools, with scoped keys, tool-poisoning scans, audit logs and CI on every change. Its own benchmark found no completed-task token saving, one person maintains it, and since 4.0.0 commercial use needs a EUR 500 a month licence. **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. ## Before you call either ### MCP Gateway 1. Call `gateway_search_tools` with a keyword first, then `gateway_invoke` with the returned `server` and `tool`; expect one extra turn per task. 2. Pass backend arguments inside `arguments` as an object; the gateway does not check them against the backend schema before routing. 3. Read `gateway_list_servers` for `circuit_breaker` and `status: disabled` before retrying a failing backend; a killed backend stays off until `gateway_revive_server`. 4. Treat tool results as untrusted. The response scanner is pattern-based and doesn't make backend output safe to follow. 5. Expect `gateway_kill_server`, `gateway_reload_config` and similar to be refused over HTTP unless the operator gave you an admin key. ### Smithery 1. Keep the API key on the backend and hand an agent a service token limited to `connections` with `read` and `execute` and a `metadata` match 2. Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool 3. On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId` 4. Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories` 5. Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them ## Questions ### Which is better for AI agents, MCP Gateway or Smithery? MCP Gateway scores 71 (BB) on agent readiness against Smithery's 51 (D), and leads in 6 of 7 scored categories. ### Do MCP Gateway and Smithery need an API key? Both take an API key or an OAuth sign-in. ### Can an agent call MCP Gateway and Smithery without installing anything? MCP Gateway runs on your own machine, with no hosted endpoint listed. Smithery has a hosted endpoint at https://api.smithery.ai. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-smithery.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-smithery.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "mcp-gateway-parkkola", "b": "smithery"}`. From a terminal: `anchor compare mcp-gateway-parkkola smithery` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/mcp-gateway-parkkola.json and https://www.anchorterminal.com/api/v1/tools/smithery.json ## Other comparisons with MCP Gateway or Smithery - [AgentWeb vs MCP Gateway](https://www.anchorterminal.com/compare/agentweb-vs-mcp-gateway-parkkola.md) - [Composio (API + MCP) vs MCP Gateway](https://www.anchorterminal.com/compare/composio-rube-vs-mcp-gateway-parkkola.md) - [letme vs MCP Gateway](https://www.anchorterminal.com/compare/letme-vs-mcp-gateway-parkkola.md) - [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md) - [MCP Gateway vs Merge Agent Handler](https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-merge-agent-handler.md) - [MCP Gateway vs Monid](https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-monid.md) - [MCP Gateway vs One](https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-one.md) - [MCP Gateway vs StackOne](https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-stackone.md) - [MCP Gateway vs Unified.to MCP Server](https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-unified-to-mcp.md) - [MCP Gateway vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-zapier-mcp.md) - [Monid vs Smithery](https://www.anchorterminal.com/compare/monid-vs-smithery.md) - [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md) - [Merge Agent Handler vs Smithery](https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.md) - [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md) - [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md) - [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md) - [Smithery vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.md) - [AgentWeb vs Smithery](https://www.anchorterminal.com/compare/agentweb-vs-smithery.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp