MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_GATEWAY_TIMEOUT | No | Proxy timeout (ms) | 30000 |
| MCP_GATEWAY_AUDIT_LOG | No | Path for the forensic audit log | disabled |
| MCP_GATEWAY_LOG_LEVEL | No | Log level (debug/info/warn/error) | info |
| MCP_GATEWAY_HTTP_TOKEN | No | Bearer token for HTTP daemon mode | unset |
| MCP_GATEWAY_AD_TRACKING | No | Set to `false` to disable ad telemetry outright | unset |
| MCP_GATEWAY_PARTNER_KEY | No | Partner attribution key — enables ad telemetry | unset |
| MCP_GATEWAY_REGISTRY_URL | No | MCP-Rating API base URL | https://mcprating.io/api/v1 |
| MCP_GATEWAY_MAX_CONNECTIONS | No | Max simultaneous connections | 10 |
| MCP_GATEWAY_CONTAINER_ISOLATION | No | Force L2 container isolation on/off | manifest decides |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_discoverA | Search the MCP-Rating registry for MCP servers. Returns servers with quality scores, trust tiers, and install information. Use this to find servers before connecting them with mcp_connect. |
| mcp_connectA | Connect to an MCP server and make its tools available. Provide either a server slug (from mcp_discover) to look up in the registry, OR an explicit command + args to spawn directly, OR a url for remote servers. |
| mcp_disconnectA | Disconnect from a connected MCP server and remove its tools. Use mcp_list_active to see connected servers. |
| mcp_list_activeA | List all currently connected MCP servers and their tools. |
| mcp_server_infoB | Get detailed information about an MCP server from the registry or a currently connected server. |
| mcp_call_toolA | Call a tool on a connected MCP server. Use this when dynamically connected tools aren't directly available. Pass the namespaced tool name (slug__toolName) and arguments. |
| mcp_gateway_healthA | Get gateway diagnostics: version, uptime, connection status, registry reachability, and per-server health. |
| mcp_sandboxA | View or customize a server's sandbox capability manifest (env/network/filesystem/subprocess access). Use action 'view' to inspect, 'set' to tighten or loosen grants (applies on next connect), or 'reset' to revert to defaults. |
| mcp_auditB | View the safety audit trail — a forensics log of what sandboxed MCP servers did and what the sandbox blocked (tool calls, blocked tools, blocked/allowed network egress, connects with granted capabilities). Use |
| mcp_profilesC | Manage named connection profiles. Profiles are presets of server connections that can be switched between (e.g., 'work', 'personal'). |
| mcp_groupsB | Manage server groups for atomic connect/disconnect of sets of servers. |
| mcp_usageC | View usage analytics for connected MCP servers — call counts, latency, error rates, and recent activity. |
| mcp_recommendB | Get MCP server recommendations. Pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes (connect vs disconnect vs call vs audit vs sandbox). However, mcp_discover and mcp_recommend both surface servers to connect to, and mcp_server_info overlaps somewhat with mcp_discover and mcp_list_active for information retrieval, creating mild boundary ambiguity.
All tools share a consistent 'mcp_' prefix and mostly follow an action-oriented pattern (mcp_discover, mcp_connect, mcp_call_tool). Minor deviations like mcp_gateway_health and mcp_server_info use noun_noun rather than verb_noun, but the set remains predictable and readable.
13 tools is well-scoped for a gateway managing server discovery, connection lifecycle, sandboxing, auditing, and analytics. Each tool appears to earn its place with no obvious redundancy.
The surface covers discovery, connect/disconnect, listing, info, tool invocation, health, sandbox, audit, profiles, groups, usage, and recommendations—a strong lifecycle. Minor gaps exist, such as no explicit reconnect/refresh or per-server tool-schema introspection beyond what mcp_server_info implies.