# MCP Gateway vs Unified.to MCP Server (slim)

> MCP Gateway scores 71 (BB) to Unified.to's 64.8 (B) for tool access for agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-unified-to-mcp.md (~6,300 tokens) · this version ~4,280 tokens · JSON https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-unified-to-mcp.json · canonical https://www.anchorterminal.com/compare/mcp-gateway-parkkola-vs-unified-to-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MCP Gateway scores 71 (BB) on agent readiness against Unified.to MCP Server's 64.8 (B), and leads in 4 of 7 scored categories. Unified.to MCP Server leads on schema & documentation, payments & pricing and transparency & trust. Both do tool access for agents.

- MCP Gateway: BB 71, rank #158 of 1266 · https://www.anchorterminal.com/tools/mcp-gateway-parkkola.min.md
- Unified.to MCP Server: B 64.8, rank #385 of 1266 · https://www.anchorterminal.com/tools/unified-to-mcp.min.md
- MCP Gateway, 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 73; Agent ergonomics, 77 against 71; Security & auth, 80 against 53; Maintenance & community, 90 against 84. Also Agent-ready, a grade of BB or better; Runs on your own machine; Free to start without a card.
- Unified.to MCP Server, good for A B2B software team that already uses or plans to use Unified's API and wants the same customer connections exposed to an LLM, with data read live from the source app. Ahead on Schema & documentation, 81 against 75; Payments & pricing, 48 against 30; Transparency & trust, 67 against 60. Also A hosted endpoint, with nothing to install.

| Category | MCP Gateway | Unified.to MCP Server |
| --- | --- | --- |
| Reliability (16%) | 87 | 73 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 81 |
| Agent ergonomics (13%) | 77 | 71 |
| Security & auth (14%) | 80 | 53 |
| Payments & pricing (10%) | 30 | 48 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 90 | 84 |
| Transparency & trust (7%) | 60 | 67 |

| Fact (where they differ) | MCP Gateway | Unified.to MCP Server |
| --- | --- | --- |
| Vendor | Mikko Parkkola | Unified API Inc. |
| Hosted endpoint | no (local only) | `https://mcp-api.unified.to/mcp` |
| Transports | stdio, Streamable HTTP, SSE (legacy), websocket | Streamable HTTP |
| Pricing | Freemium | Paid |
| 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 service under Unified.to's Terms of Service. The linked repository is sample client code |
| Tools exposed | 11 | none |
| MCP registry | `io.github.MikkoParkkola/mcp-gateway` | `to.unified/core` |
| Last release | 2026-10-06 | 2026-10-30 |
| Privacy policy last updated | no document linked | 2026-10-02 |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | 65 stars, 49 npm/wk | 22k npm/wk |
| Agent reviews | none | 2.5/5 (4) |

Why the edge:
- Security & auth, MCP Gateway +27: 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.); Unified.to MCP Server 53 (The workspace API key reaches all connections and the whole account, and it is still the credential for a connection's data tools. Since the 9 October check the docs describe OAuth sign-in for MCP clients, with dynamic client registration, PKCE (`S256`), `mcp:read` and `mcp:write` scopes that filter the tool list and 24-hour tokens, but it serves only the Core management tools. With the connection-scoped token and the scoped, one-hour enterprise tokens this gives 25, up from 22. Ten off because `?token=` in the URL remains a documented option, deprecated with no end date (15). `permissions` and `tools` limit the tool list, OAuth and enterprise scopes hide tools a token may not call, and connections are isolated from one another. No approval step for writes was found (14). Tool results are third-party content. `hide_sensitive` removes PII, and no prompt-injection guidance was found (4). API call logs kept 30 to 365 days by plan, readable through management tools and streamable to Datadog on Pro and Scale. The docs warn that a workspace key leaves no per-person audit trail (10). SOC 2 Type II and yearly penetration tests are stated, per the 9 October check. security.txt still returns 404, no bounty or disclosure policy was found, and the trust centre was not read (10). 15 + 14 + 4 + 10 + 10 = 53.)
- Payments & pricing, Unified.to MCP Server +18: 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.); Unified.to MCP Server 48 (No x402, MPP or L402 (0). Plan prices and overage rates per 1,000 API calls are public, and each tool call counts as one request. Two off because every plan price is shown with a plus sign and Enterprise is on contract (18). The pricing page now says the 30-day free trial needs no credit card, and an agent's own signup starts a 30-day Test plan with Sandbox integrations (20, up from 12). The agent signup page, updated 14 October 2026, lets an agent call `POST /agent/signup` with no credential and get a workspace API key, and since 17 October `signup_unified_workspace` on `/mcp?signup=true` does the same. The workspace reaches only Sandbox integrations with mock data, and a person must claim it to activate Production integrations or keep it past 30 days. An agent can't reach real data on its own, which sits below mem0's and sponge-wallet's unclaimed accounts that do real work (20) and pulumi-esc's and maritime's temporary accounts with real access (15). Half, as context-dev and typesense, where a person completes the step that makes access useful (10 of 20, up from 0). 0 + 18 + 20 + 10 = 48.)
- Reliability, MCP Gateway +14: 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.); Unified.to MCP Server 73 (Read with the hosted lines. status.unified.to on Honeybadger lists seven components, the API and the admin app in three regions and the authentication page. The MCP server has no component of its own (20). Re-read on 2 November 2026, the page lists one incident in three months, API performance issues on 13 August 2026, resolved in an hour, and none in September, October or November. Its detail page is closed by robots.txt and was not read, so it is counted as minor (20). Workspace limits are published per plan, from 500 to 10,000 requests a minute (15). The docs describe exponential backoff with jitter on 429 and say Unified does not queue or retry. No `Retry-After` header and no idempotency key were found (8). No uptime SLA is published. The pricing page says SLAs come with a custom Enterprise plan (0). The server launched on 1 June 2025 and carries no beta label (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.)
- Transparency & trust, Unified.to MCP Server +7: 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.); Unified.to MCP Server 67 (The editorial half. Closed service under Terms of Service that name Unified API Inc. and Ontario law. Two off because the terms carry no date and bar sending financial or medical information and birth dates through a service sold for accounting and HR data (13). The privacy policy has an MCP section, says end-customer data is not stored and no models are trained, and gives retention periods by plan. The DPA of 19 March 2026 promises breach notice within 72 hours and deletion within a reasonable period on request. The security page says no data is stored at rest, ever, while the policy lists stored credentials, configuration and logs, and the page says Unified runs on AWS while the sub-processor list also names Render (22). No deprecation policy. `?token=` carries a `Deprecation` header with no end date, a field deprecation notice was published in November 2025, and SSE was removed on the day it was announced (8). Ten sub-processors with locations, dated 2 October 2025, and three named regions. The DPA gives 15 days' notice of new sub-processors on a best-efforts basis (18). The terms, privacy policy, DPA and sub-processor list were not re-read on 2 November 2026. 13 + 22 + 8 + 18 = 61.)
- Schema & documentation, Unified.to MCP Server +6: MCP Gateway 75 (Every meta-tool declares a typed JSON Schema input with required fields, read from src/gateway/meta_mcp_tool_defs.rs, and server.json is published to the official registry. `gateway_invoke` passes backend `arguments` as an open object by design (22 of 25). llms.txt at the repository root, and Markdown docs in the tree (10). Descriptions say what each tool does and when (search first, then invoke; kill and revive say what they change for every session), and the initialize preamble names the discovery order. Backend tool descriptions come from the user's servers and aren't the gateway's (14 of 20). `gateway_list_tools` has an enum on `role`, `gateway_search` caps `limit` at 25 and `detail` is an enum, `nonce` has length bounds; `limit` on `gateway_search_tools` has no maximum (11 of 15). README, QUICKSTART, an annotated gateway-full.yaml and a troubleshooting section; errors are described in prose, with did-you-mean suggestions, and there is no error reference (8 of 15). Semver over the CLI and config file, stated in the README, and a long changelog, less for the missing 3.3.0 section and the misdated 1.0.0 and 2.0.0 entries (10 of 15). 22 + 10 + 14 + 11 + 8 + 10 = 75.); Unified.to MCP Server 81 (One credential-free `tools/list` preview for HubSpot on 2 November 2026 returned 81 tools, each with a JSON Schema input and 68 with an output schema. The API has a published OpenAPI 3.0 file, which we did not read (25). llms.txt on the docs and the site, a full-text file, and a Markdown twin of every docs page (10). Tool descriptions state the action, what is returned, what is required and which sibling tool to use. They follow one template and say nothing about provider differences (15). The 81 inputs hold 420 properties and 135 enums with no open objects at the top level, and since 9 October create and update tools list only the fields the integration accepts. `limit` and `offset` still have no bounds and some filters are plain strings (12). Client set-up examples for several hosts and a table of HTTP status codes. No per-tool examples, and MCP error results are not documented (8). A dated MCP changelog, with 13 entries from 21 September to 30 October 2026. The server has no version scheme beyond the registry's 1.0.0 (11).)
- Agent ergonomics, MCP Gateway +6: 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.); Unified.to MCP Server 71 (One HubSpot connection lists 81 tools, about 133 KB of definitions without output schemas and 403 KB with them, which scores 5. Eight back for the `tools` and `permissions` filters, which take wildcards such as `list_*,get_*` and which the docs tell users to set (`defer_tools` applies only to the REST tool list) (13). List tools take `limit`, `offset`, a `fields` selection, `updated_gte`, `sort`, `order` and `query`. Pages hold 100 records at most and there is no cursor or total (18). An unauthenticated call to a tool returns an error asking the client to authenticate, and the REST status table explains 401, 403, 429 and 501. Tool error results are not documented (11). All 81 previewed tools set `readOnlyHint`, `destructiveHint`, `idempotentHint` and `openWorldHint`. Creates are marked not idempotent and there is no idempotency key (15). 62 required fields across 420 properties, and API SDKs in seven languages. Every option travels as a URL parameter (14).)