@onyxsecurity/mcp-gateway
npm
v2.1.36
Published by @onyxsecurity — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
A TypeScript SSE proxy for MCP servers that use stdio transport.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/stdio-WPzVi5vO.js:12`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ]);return i.name=e.name,Function(`fn`,`log`,`deprecate`,`message`,`site`,`"use strict" return function (`+n+`) {log.call
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/stdio-WPzVi5vO.js
In the server's implementation (`dist/main-cQGW6pn2.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: awnSync as xe}from"node:child_process";import{createInterface as E}from"node:readline";import{PassThrough as D,Transform
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/main-cQGW6pn2.js
In the server's implementation (`dist/secretstore-B7UBzLo4.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: execFile as o}from"node:child_process";const s=`onyx-mcp-gateway`,c=`default`,l=`/Library/Keychains/System.keychain`,u=2
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/secretstore-B7UBzLo4.js
In the server's implementation (`dist/transportDetection-BRl6-9Sh.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: execFile as g}from"node:child_process";async function _(e){let t=e.toString(),n=p(),r=x(t);return new Promise((e,i)=>{le
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/transportDetection-BRl6-9Sh.js
In the server's implementation (`dist/helpers-BrpBfS5F.js:30`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: r){_=e;return}}else e=O.require(t);se(e)}catch(t){t.name===`PermissionDenied`?_=t:e[n]&&(_=Error(m(`Invalid JSON config
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/helpers-BrpBfS5F.js
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.36 latest |
A 92/100 | 5 | 1.13.0 | 2026-09-07 |
v2.1.31 |
A 92/100 | 5 | 1.13.0 | 2026-09-04 |
v2.1.25 |
A 92/100 | 5 | 1.13.0 | 2026-09-01 |
v2.1.23 |
A 92/100 | 5 | 1.13.0 | 2026-08-31 |
v2.1.21 |
A 92/100 | 5 | 1.13.0 | 2026-08-30 |
v2.1.19 |
A 92/100 | 5 | 1.13.0 | 2026-08-25 |
v2.1.15 |
A 92/100 | 5 | 1.12.1 | 2026-08-24 |
v2.1.14 |
A 92/100 | 5 | 1.12.1 | 2026-08-23 |
v2.1.11 |
A 92/100 | 5 | 1.12.1 | 2026-08-19 |
v2.1.10 |
A 92/100 | 5 | 1.12.1 | 2026-08-18 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @onyxsecurity/mcp-gateway --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 16 side by side →
MCP Gateway for exposing VAT agents through Model Context Protocol
NestJS MCP Gateway - Proxy, route, and aggregate multiple MCP servers
The Kirha MCP Gateway provides unified access to Kirha Tool Planning through the Model Context Protocol (MCP), enabling advanced tool composition and execution for LLM interfaces.
MCP Gateway for Blaxel
Policy enforcement, tamper-evident audit trail, and kill switch for any MCP server — a drop-in governance proxy
Personal MCP Gateway - aggregate multiple MCP servers into one stdio interface
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.