io.mcprating/gateway
NPM · @MCP-RATING/GATEWAY · SCANNED SEP 21
Discover, judge and safely run any MCP server: 57k+ scored servers, sandboxed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mcprating/mcp-gateway). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1903 tokens (~146/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.mcprating/gateway MCP server?
io.mcprating/gateway runs locally as an npm package, launched with npx -y @mcp-rating/gateway. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mcp-rating/gateway
claude mcp add io-mcprating-gateway -- npx -y @mcp-rating/gateway
{
"mcpServers": {
"io-mcprating-gateway": {
"command": "npx",
"args": [
"-y",
"@mcp-rating/gateway"
]
}
}
} {
"servers": {
"io-mcprating-gateway": {
"command": "npx",
"args": [
"-y",
"@mcp-rating/gateway"
]
}
}
} codex mcp add io-mcprating-gateway -- npx -y @mcp-rating/gateway
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-mcprating-gateway": {
"type": "local",
"command": [
"npx",
"-y",
"@mcp-rating/gateway"
],
"enabled": true
}
}
} openclaw mcp add io-mcprating-gateway --command npx --arg -y --arg @mcp-rating/gateway
mcp_servers:
io-mcprating-gateway:
command: "npx"
args: ["-y", "@mcp-rating/gateway"] {
"McpServers": {
"io-mcprating-gateway": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mcp-rating/gateway"
]
}
}
} assistant mcp add io-mcprating-gateway -t stdio -c npx -a -y @mcp-rating/gateway
{
"mcpServers": {
"io-mcprating-gateway": {
"command": "npx",
"args": [
"-y",
"@mcp-rating/gateway"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@mcp-rating/gateway@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mcprating/mcp-gateway |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mcprating/mcp-gateway/.github/workflows/publish.yml@refs/tags/v0.2.2 |
| Rekor log index | 2625193543 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c812e6eb99561842db94666f3abd878ebbc7a4a6cb427d409f07187aa83a9ce1ca88bafceec7d65b6b7319d4f16497860ef6306e3c275df4376ef02d6 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mcp_audit ~129
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 `securityOnly: true` to see only blocks and errors.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | Filter to a single event type |
| limit | number | – | Max events to return (default 50, newest first) |
| securityOnly | boolean | – | Show only security-relevant events (blocks + errored calls) |
| slug | string | – | Filter to a single server slug |
No output schema declared.
No examples provided.
mcp_call_tool ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Tool arguments as a JSON object |
| name | string | yes | Namespaced tool name: "server-slug__tool-name" (as shown by mcp_connect or mcp_list_active) |
No output schema declared.
No examples provided.
mcp_connect ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Command arguments (e.g., ['-y', '@modelcontextprotocol/server-everything']) |
| command | string | – | Explicit command to spawn (e.g., 'npx'). Use when server is not in registry. |
| confirmed | boolean | – | Set to true to confirm connection to community/unknown trust tier servers. Required when the initial connect returns a confirmation warning. |
| env | object | – | Additional environment variables for the server process |
| saveProfile | boolean | – | Set to true to save this connection as an auto-connect profile. The server will auto-reconnect on gateway restart. |
| slug | string | – | Server slug from MCP-Rating registry (e.g., '@modelcontextprotocol/inspector') |
| transportType | string | – | Transport type. Defaults to 'stdio' for command-based, auto-detected from URL scheme if url is provided. |
| url | string | – | URL for remote transports (SSE, WebSocket, Streamable HTTP). Use instead of command for remote servers. |
No output schema declared.
No examples provided.
mcp_disconnect ~45
Disconnect from a connected MCP server and remove its tools. Use mcp_list_active to see connected servers.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Server slug of the connected server to disconnect |
No output schema declared.
No examples provided.
mcp_discover ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category slug (e.g., 'developer-tools', 'data-databases') |
| limit | number | – | Max results (default 10) |
| query | string | yes | Search query (server name, description, or capability) |
No output schema declared.
No examples provided.
mcp_gateway_health ~30
Get gateway diagnostics: version, uptime, connection status, registry reachability, and per-server health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mcp_groups ~171
Manage server groups for atomic connect/disconnect of sets of servers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: list, create, delete, add_server, remove_server, connect (all in group), disconnect (all in group), show (details) |
| args | array | – | Command arguments (for add_server with stdio) |
| command | string | – | Explicit command for the server (for add_server with stdio) |
| description | string | – | Group description (optional, for create) |
| name | string | – | Group name (required for all actions except list) |
| slug | string | – | Server slug to add/remove from a group |
| transportType | string | – | Transport type (for add_server) |
| url | string | – | Server URL (for add_server with SSE/WS/HTTP) |
No output schema declared.
No examples provided.
mcp_list_active ~20
List all currently connected MCP servers and their tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mcp_profiles ~201
Manage named connection profiles. Profiles are presets of server connections that can be switched between (e.g., 'work', 'personal').
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: list (all profiles), create (new profile), delete, add_server (add a server to profile), remove_server, switch (activate profile), show (details of a profile) |
| args | array | – | Command arguments (for add_server with stdio) |
| command | string | – | Explicit command for the server (for add_server with stdio) |
| description | string | – | Profile description (optional, for create) |
| name | string | – | Profile name (required for create, delete, add_server, remove_server, switch, show) |
| slug | string | – | Server slug to add/remove from a profile |
| transportType | string | – | Transport type (for add_server) |
| url | string | – | Server URL (for add_server with SSE/WS/HTTP) |
No output schema declared.
No examples provided.
mcp_recommend ~147
Get MCP server recommendations. Pass `query` to describe a goal or task (e.g. "file sync with cloud storage", "manage GitHub issues"). Omit `query` to get suggestions based on your recent tool-call patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category slug to filter (e.g. 'developer-tools', 'data-databases'). Only used with `query`. |
| limit | number | – | Maximum number of recommendations (default 5, max 20) |
| query | string | – | Free-text goal or task. When provided, recommends servers that match this intent using semantic/keyword/expansion search. When omitted, recommends based on usage history. |
No output schema declared.
No examples provided.
mcp_sandbox ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | view = inspect manifest; set = override grants; reset = revert to defaults |
| enforcement | string | – | [set] Isolation level. l2-container requires Docker/Podman. |
| envAllow | array | – | [set] Environment variable NAMES the server may receive, e.g. ['GITHUB_TOKEN'] |
| fsRead | array | – | [set] Absolute paths the server may read |
| fsWrite | array | – | [set] Absolute paths the server may write |
| network | string | – | [set] Network mode. 'none' = no network, 'allowlist' = only listed hosts, 'all' = unrestricted |
| networkAllow | array | – | [set] Allowed host:port patterns for allowlist mode, e.g. ['api.github.com:443', '*.example.com'] |
| slug | string | yes | Server slug (as shown by mcp_list_active or mcp_discover) |
| subprocess | boolean | – | [set] Whether the server may spawn subprocesses |
No output schema declared.
No examples provided.
mcp_server_info ~41
Get detailed information about an MCP server from the registry or a currently connected server.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Server slug (from registry or connected server) |
No output schema declared.
No examples provided.
mcp_usage ~127
View usage analytics for connected MCP servers — call counts, latency, error rates, and recent activity.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action: stats (default — summary), recent (recent calls), slow (slow calls), reset (clear all data) |
| limit | number | – | Limit number of results for 'recent' and 'slow' actions (default: 20) |
| slug | string | – | Filter stats to a specific server slug. Omit for global stats. |
| threshold | number | – | Latency threshold in ms for 'slow' action (default: 5000) |
No output schema declared.
No examples provided.
What is the io.mcprating/gateway MCP server?
io.mcprating/gateway is an MCP server listed in the public MCP registry as io.mcprating/gateway. Discover, judge and safely run any MCP server: 57k+ scored servers, sandboxed. This page covers its npm package (@mcp-rating/gateway).
Is the io.mcprating/gateway MCP server safe to use?
io.mcprating/gateway scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.mcprating/gateway MCP server expose?
io.mcprating/gateway exposes 13 tools: mcp_discover, mcp_connect, mcp_disconnect, mcp_list_active, mcp_server_info, and 8 more. Their descriptions and schemas cost roughly 1,636 tokens of context every time the server is loaded.
Is the io.mcprating/gateway MCP server still maintained?
io.mcprating/gateway is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.mcprating/gateway MCP server under?
io.mcprating/gateway declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.