The safeguards map / 3.3 Gateways
MCP Gateway Registry
Drafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
A reverse proxy and registry for Model Context Protocol (MCP) servers that validates OAuth access with fine-grained scopes and keeps an inventory and audit trail of the servers and agents behind it.
Where it sits
3.3 Gateways (primary): Sits on the path between agents and MCP servers as a reverse proxy that validates authentication, routes to backends and applies scopes the owner defines.
a generic nginx reverse proxy: TLS, auth validation, routing to backends
captured
OAuth against your existing IdP (Keycloak, Entra ID, Okta, Auth0, Cognito, PingFederate) with fine-grained
captured
you can connect OAuth-protected SaaS MCP servers such as Slack, Atlassian, and GitHub
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- agentsoftware
- Used by
- those who run it
- Runs
- at runtime
- Policy comes from
- owner-entered settings
- Traffic it sees
- tool calls (MCP)
- Can the agent bypass it
- depends
Handoffs
produces Runtime records: OTLP
Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.