MCP Gateway
OCI · GHCR.IO/MIKKOPARKKOLA/MCP-GATEWAY:3.5.1
Universal MCP gateway with Meta-MCP discovery, routing, and REST API capabilities.
Available components
Last scanned (10 hours ago)
Scores higher than 91% of OCI servers
Category Developer Tools
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 61 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1159 tokens (~68/item across 17 items; 15 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (7% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 0
- Provenance: unverified → fail ▼ security
- 1 Nov 26 0
- Provenance: fail → unverified ▼ security
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 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.
- 17 Oct 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.
- 15 Oct 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.
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 5 Nov 2026 · Analysed oci/ghcr.io/mikkoparkkola/mcp-gateway:3.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
gateway_cost_report Cost Report ~110
Return current session and API-key spend. Includes total cost, call count, and breakdown by backend and tool. Per-key totals are shown for 24 h / 7 d / 30 d rolling windows.
| Name | Type | Req | Description |
|---|---|---|---|
| include_all_keys | boolean | – | Return all API key accumulators (admin view). Default false. |
| include_all_sessions | boolean | – | Return all active sessions (admin view). Default false. |
| session_id | string | – | Specific session ID to report on. Defaults to current session. |
No output schema declared.
No examples provided.
gateway_get_profile Get Routing Profile ~24
Show the active routing profile for this session and what it allows or denies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gateway_get_stats Get Gateway Statistics ~56
Get usage statistics including invocations, cache hits, token savings, and top tools
| Name | Type | Req | Description |
|---|---|---|---|
| price_per_million | number | – | Token price per million for cost calculations (default 15.0 for Opus 4.6) |
No output schema declared.
No examples provided.
gateway_invoke Invoke Tool ~77
Invoke any tool on any backend server. Routes through the gateway's auth, rate-limit, caching, and failsafe middleware. Use gateway_search_tools first to discover the right tool and server.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Tool arguments |
| server | string | yes | Backend server name |
| tool | string | yes | Tool name to invoke |
No output schema declared.
No examples provided.
gateway_kill_server Kill Server ~51
Immediately disable routing to a backend server (operator kill switch). The server's tools remain visible in search/list but are marked as disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | Name of the backend server to disable |
No output schema declared.
No examples provided.
gateway_list_disabled_capabilities List Disabled Capabilities ~72
List capabilities that have been automatically disabled due to a high error rate. Each entry shows the backend, capability name, and how long it has been suspended. Disabled capabilities auto-recover after the configured cooldown period (default 5 min). Use gateway_revive_server to manually re-enable an entire backend immediately.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gateway_list_profiles List Tool Profiles ~48
List all available routing profiles with their descriptions. Use gateway_set_profile to switch to a profile that narrows the visible toolset to the current task (e.g. "coding", "research").
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gateway_list_servers List Servers ~30
List all 0 connected MCP backend servers with their status, tool count, and circuit-breaker state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gateway_list_tools List Tools ~118
List tools from a specific backend, or omit server to list all 0 tools across 0 backends. Returns names and descriptions — use gateway_search_tools for ranked results with full schemas.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Optional: only return tools of this role. selector=search/list, extractor=get/read, enricher=adds context, action=mutates state. Untagged tools are classified by name + read-only hint. |
| server | string | – | Name of backend server. Omit to list ALL tools across all backends. |
No output schema declared.
No examples provided.
gateway_reload_capabilities Reload Capabilities ~73
Re-read all YAML capability files from disk and rebuild the capability backend's tool surface. Returns the new total. Useful when an agent has just written a new capability YAML and wants it usable without restarting the gateway. Clients should re-list capability tools to see additions; `tools/list_changed` notification is a follow-up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gateway_revive_server Revive Server ~48
Re-enable routing to a previously disabled backend server. Also resets the error budget so the server gets a clean slate.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | Name of the backend server to re-enable |
No output schema declared.
No examples provided.
gateway_run_playbook Run Playbook ~49
Execute a multi-step playbook (collapses multiple tool calls into one invocation)
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Playbook input arguments |
| name | string | yes | Playbook name to execute |
No output schema declared.
No examples provided.
gateway_search_tools Search Tools ~100
Search 0 tools across 0 servers by keyword. Returns ranked matches (name, description, score) while avoiding the prompt bloat of loading every tool definition upfront. Ranking diagnostics are omitted unless explain is true. Supports multi-word queries and synonym expansion.
| Name | Type | Req | Description |
|---|---|---|---|
| explain | boolean | – | Include ranking diagnostics (reasons and signals). Default false. |
| limit | integer | – | Maximum results (default 10) |
| query | string | yes | Search keyword |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | Ranked list of matching tools |
No examples provided.
gateway_set_profile Set Routing Profile ~54
Switch the active routing profile for this session. A routing profile restricts which tools and backends are available.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | Name of the routing profile to activate (e.g. "research", "coding") |
No output schema declared.
No examples provided.
gateway_set_state Set Workflow State ~92
Transition the session to a new workflow state. Capabilities with a non-empty `visible_in_states` list will only appear in tools/list when the session is in a matching state. Tools without `visible_in_states` are always visible. Returns the previous state, new state, and visible tool count.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Target workflow state name (e.g. "checkout", "payment", "default") |
No output schema declared.
No examples provided.
How do I install the MCP Gateway server?
MCP Gateway runs locally as a container image, launched with docker run --rm -i ghcr.io/mikkoparkkola/mcp-gateway:3.5.1 serve --stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mikkoparkkola/mcp-gateway:3.5.1
claude mcp add mikkoparkkola-mcp-gateway -- docker run --rm -i ghcr.io/mikkoparkkola/mcp-gateway:3.5.1 serve --stdio
What is the MCP Gateway server?
MCP Gateway is listed in the public MCP registry as io.github.MikkoParkkola/mcp-gateway. Universal MCP gateway with Meta-MCP discovery, routing, and REST API capabilities. This page covers its container image (ghcr.io/mikkoparkkola/mcp-gateway:3.5.1).
Is the MCP Gateway server safe to use?
MCP Gateway scores 54 out of 100 on VerifyMCP. 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 MCP Gateway server expose?
MCP Gateway exposes 15 tools: gateway_list_servers, gateway_list_tools, gateway_search_tools, gateway_invoke, gateway_get_stats, and 10 more. Their descriptions and schemas cost roughly 1,002 tokens of context every time the server is loaded.
Is the MCP Gateway server still maintained?
MCP Gateway is still listed as active in the MCP registry. We last reached this channel on 5 November 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 MCP Gateway server under?
MCP Gateway declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the MCP Gateway server?
VerifyMCP ran 12 checks on MCP Gateway, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about MCP Gateway: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.