Features
One checkpoint between your agents and your tools — every mechanism below is in the v1 code, not on a roadmap.
support-bot calls github:list_issues
The agent authenticates with its own key — never the upstream credential — and the gateway runs the same checks, in the same order, on every call.
github:list_issues is named in this agent’s allowlist — the call may proceed.
Checked against the agent’s per-minute limit and the plan’s monthly quota on forwarded calls.
The stored upstream auth header is injected server-side and the call is forwarded.
Agent, server, tool, outcome and latency are logged — secret-looking arguments redacted first.
One endpoint for every MCP server
Register your streamable-HTTP MCP servers once. Agents connect to a single GateRelay URL and see the union of tools, namespaced server__tool — swap or remove a server in one place, for every agent at once.
Per-agent keys, deny-by-default
Mint one key per agent. Keys are stored only as SHA-256 hashes. Allowlist patterns: *, server:*, or server:tool — an empty allowlist means the agent can see and call nothing.
Server-side credential injection
Store each upstream's auth header once; the gateway injects it on forwarded calls. Agents authenticate with their own scoped key and never touch the real credentials.
Rate limits + monthly quotas
A sliding-window rate limit per agent and a plan quota on forwarded calls. Over-limit calls return a clear JSON-RPC error and are audited — they don't silently burn your budget.
Audit log with redaction
Every decision is logged: timestamp, agent, server, tool, outcome, latency. Arguments are redacted for secret-looking keys (password, token, api_key, …) before storage. Export as CSV anytime.
Upstream failure isolation
A dead upstream is skipped in tool listings and its calls audit as errors — the gateway and your other servers keep working. Upstream JSON-RPC errors pass through with their original code and message.
How we compare
Competitor prices verified October 2026.
| Tool | Entry price | The catch |
|---|---|---|
| GateRelay Team | $29/mo | Hosted MCP governance: allowlists, rate limits, quotas, redacted audit |
| TrueFoundry Pro | $25/user/mo [verified Oct 2026] | Gateway is one component of a full ML platform, and MCP tool calls share the same meter as LLM requests |
| Zuplo Builder | $25/mo [verified Oct 2026] | API-gateway add-on; metered requests; VPC/tunnels are paid add-ons, Enterprise from ~$1,000/mo |
| MintMCP / Runlayer | sales call [verified Oct 2026] | No public self-serve pricing at all |
| ContextForge (OSS) | free, self-hosted | You run it, patch it, and build your own audit/quota layer |