Cortex Gateway MCP server
online · 100% uptimeSelf-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.
12 stars
Reviews
Write oneNobody has reviewed Cortex Gateway yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cortex Gateway tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- Live reliabilityremote reachable in 508ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 34 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Cortex Gateway compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 229 ms
- faster than 59% of 30,031 servers
- GitHub stars
- 12
- more than 89% of 28,688 servers
Install Cortex Gateway in Claude Code, Cursor or VS Code
claude mcp add --transport http cortex-gateway https://mcp.cortex-gateway.dev/mcp
What the publisher says
From the Cortex Gateway repository's README, as published. We do not edit it. Read it on GitHub
Cortex Gateway
A federated MCP gateway: one spec-compliant, OAuth-protected MCP server in front of N plain-HTTP backends.
Your business apps stay ordinary web services. Each one exposes a single POST /api/cortex/backend endpoint (a ~120-line contract, no MCP library, no stdio). The gateway discovers their tools, merges them into one MCP catalog, enforces OAuth 2.1 + scopes, routes tools/call to the owning backend, and keeps a pseudonymized audit trail.
Built for one requirement: everyone in a company should be able to hand their own agent the keys — with exactly that person's rights, nothing more, nothing less. And when agents become autonomous assistants, the answer stays the same: the agent borrows the person's identity, the apps keep enforcing that person's rights. The gateway decides nothing, so there is nothing new to trust.
Put another way: zero-trust principles for AI agents — the missing link between your IAM (who your users are, what they may do) and the MCP ecosystem (how agents call tools). Not a full ZTNA product; the identity-and-access layer for agents.
A backend is a dedicated MCP reduced to its essence: a tool catalog plus tool invocation (and optional prompts/resources) over bare HTTP JSON-RPC — the transport and lifecycle machinery (initialize, sessions, SSE, version negotiation) lives once, in the gateway. Because the contract is a semantic subset of MCP, a native MCP server can also be federated through the built-in MCP→backend proxy adapter (docs/mcp-adapter.md).
[MCP agent: Claude Desktop / claude.ai Custom Connector / any MCP client]
│ HTTPS + OAuth 2.1 JWT (Bearer)
▼
[cortex-gateway] ←— thin gateway, no business logic
│ HTTPS + the same JWT propagated (RFC 8707)
▼
[your backends] ←— domain owners, plain HTTP, own their ACLsWhy
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Cortex Gateway: common questions
- Is Cortex Gateway MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Cortex Gateway safety report
- How do I install Cortex Gateway?
- It runs remotely at mcp.cortex-gateway.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Cortex Gateway need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Cortex Gateway maintained?
- The last commit was 74 days ago (2026-08-22). The latest release is v0.2.0.
- Is Cortex Gateway up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Cortex Gateway?
- Servers from other publishers that do the same job: OpenWork MCP Gateway MCP server.
- How does Cortex Gateway compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 229 ms (faster than 59% of 30,031 servers). Full comparison.
Alternatives to Cortex Gateway
Same job from other publishers: the closest match first, then the best rated.
OpenWork MCP GatewayYour OpenWork org's skills, plugins, workflows, and connections through one OAuth MCP URL.not reviewedEstablishedA