@winstonsayno/mcp-gateway
It exited or failed before answering, and its output does not say what it needs. Run 2026-11-16.
Needs to start: unclear. Its error said: server exited with code 1
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @winstonsayno/mcp-gateway@17.0.7
Installing a package runs its code. Use a sandbox for anything you have not read.
What it said when it did not start
Rewrite a config file to schema v11 (or --to 10
/ 9 / 8 / 7 / 6 / 5 / 4), keeping comments;
prints the changes
config Config schema tools: migrate a schema v11 file
to schema v12 (14.0), diff, roll back
bench [options] Benchmark an in-process gateway with a local
echo server (REST, auth, cache, /mcp)
plugin Plugins: init, doctor (15.2), migrate --to v6
(16.9), keygen, sign, verify (--rebuilt:
reproducible check, 15.2)
pq Post-quantum (ML-DSA) hybrid keys — EXPERIMENTAL
conformance [options] <url> Run the MCP conformance suite against a
Streamable HTTP endpoint (e.g.
http://127.0.0.1:8080/mcp)
tasks Durable task runs (14.4): list, inspect, resume,
cancel, approve / deny, and the failure queue
(DLQ)
regions Multi-region consistency (14.5): report, health,
replicated revocations
edge Edge autonomy (14.6): offline report, queue,
reconcile
gitops GitOps (14.7): render config directories, env
diffs, signed releases, plan / apply / status
help [command] display help for command
Written by the package or by npm, not by this site.
Install facts
| License | MIT |
|---|---|
| Needs | node >=24.0.0 |
| Source | github.com/HarrisonCN/mcp-gateway |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-uatLsrC6gpNIbIGLDAoz1aEuy2rtqMGPl3dNywUrC9YNRt8F8Tk0Uw9Vhaeuj6ARvYXmx/JqZe1N18I9pEdeVg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40winstonsayno/mcp-gateway)
New version out? Ask for a fresh report.