MCP Gateway vs StackOne

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.

StackOne 70

The editorial half. Closed service under SaaS terms that name StackOne Technologies Limited, with the Agent SDKs and Defender under Apache-2.0 (17). The DPA of 15 January 2025 promises deletion within 30 days of termination and breach notice within 48 hours, and the AI Services Addendum says AI providers may not train on customer data. The privacy policy of December 2023 says data is stored in the EEA while projects can be created in a US region, and it gives 30 and 90 day retention periods side by side. The SaaS terms let StackOne use anonymised usage data to improve the Service (18). No deprecation policy for the API was found. Preview functions can be withdrawn at any time, and the Starter plan can change with 30 days' notice on a reasonable-efforts basis. Connector versions can be pinned (5). Three hosting regions are named with their data centres. The sub-processor list is on the trust centre, which we could not read. The DPA gives 14 days to object to a new sub-processor (10).

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.

StackOne 71

OAuth per user with one-hour access tokens, a 90-day grant and revocation, and project API keys with scopes that can be disabled or deleted, would score 30. Ten off because session token URLs carry the access in the query string as a documented option, with a one-year default expiry (20). Connector profiles enable individual actions, users grant accounts and actions at consent, the Credentials scope is off by default, and Policies deny tools, mask fields and bound values on Team and Enterprise. Policies skip API-key calls, and no approval step at the gateway was found (16). Defender scans tool results and is on for new projects, in Monitor mode by default, which changes nothing. Large responses skip scanning by default (12). Action logs on every plan (one day on Starter), login security logs and Advanced Logs with credential masking. The Logs API, audit logs and SIEM export are Enterprise only on Gateway plans (11). SOC 2 Type II and HIPAA are stated on the pricing and contact pages, and the DPA promises breach notice within 48 hours. Since 26 October 2026 the Defender repository carries a SECURITY.md with private reporting, security@stackone.com and a three-business-day acknowledgement, which covers that package only. security.txt returned 404, no bounty or platform-wide disclosure policy was found, and the trust centre answered with a bot check (12).

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.

StackOne 38

No x402, MPP or L402 (0). Credit prices are public. One credit per tool call or API call, extra credits at $60 per 20,000 on Starter and $20 per 20,000 on Team, and Team at $600 a month. Two off because the per-seat price sits only in the calculator's markup, the rates for advanced capabilities aren't published, and the Service Consumption Schedule and the pricing page disagree on failed calls (18). Free plans on both models with no card, per the pricing page (20). A person signs up in the dashboard, and no keyless or programmatic signup route was found (0).

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.

StackOne 80

Read with the hosted lines. status.stackone.com on incident.io lists the Web Dashboard, the API in three regions and the Connectors Hub (20). Its feed, read on 1 November 2026, lists one incident in the last 90 days, increased API error rates in EU-WEST-1 on 13 August, affecting the EU API and the dashboard. One region is partial, so minor incidents only (20). API keys are limited to 1,000 requests a minute (15). 429 responses carry Retry-After in seconds, and StackOne retries a provider's 429 up to five times within a 60-second request lifetime before returning 429 or 408. No idempotency key or retry guidance for writes was found (10). The pricing page lists an uptime SLA on Enterprise with no figure, and the Starter plan has none (5). MCP and the RPC endpoint carry no beta label. A2A is in open beta (10).

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.

StackOne 84

Changelog entries up to 29 October 2026 and @stackone/ai v3.1.0 and stackone-ai (Python) v3.0.0 on 29 October (30). Dated changelog entries from 3 August to 29 October, Node SDK 3.0.0 and 3.1.0, Python SDK 3.0.0 and Defender 0.9.0 to 0.9.4 in the last 90 days (20). A closed service with a dated changelog and in-app chat and email support. GitHub issues were not readable on 1 November, so the 9 October reading of 7 open issues stands (11). com.stackone/mcp is in the official MCP registry under the vendor's domain namespace, version 1.0.1 of 17 August 2026 (15). The SDK repositories carry CI workflows, lockfiles and release automation, and the CI state wasn't read (8).