supergateway — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of npm/supergateway: Does the gateway now default to safe network exposure and provide explicit authentication controls?

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Deploy or connect MCP servers across different transports

What we know

MCP transport bridge for stdio, SSE, WebSocket and Streamable HTTP.

Maintenance / activity evidence

Supergateway v4.1.0 was released 2026-09-30.

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Transport gateway; downstream server tools and risks inherited. Bind locally and authenticate before public exposure. Complete write authority is not verified.
Authentication not yet verified.
A network-exposed gateway can expose all capabilities of its attached MCP server. Do not bind publicly without independent access controls.

A network-exposed gateway can expose all capabilities of its attached MCP server. Do not bind publicly without independent access controls.
Advisory/security review not completed; no safety badge.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

2,887 shared-repository stars · 583.1k package downloads / 30 days

Stars observed Oct 9, 2026. Downloads observed Oct 9, 2026.

Repository total for supercorp-ai/supergateway; not package-specific.

Exact npm package supergateway; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Does the gateway now default to safe network exposure and provide explicit authentication controls?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

A network-exposed gateway can expose all capabilities of its attached MCP server. Do not bind publicly without independent access controls.
Advisory/security review not completed; no safety badge.
Transport gateway; downstream server tools and risks inherited. Bind locally and authenticate before public exposure.
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Converts local MCP processes to network endpoints; network exposure and downstream tool authority require operator configuration.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
exact authentication contract
first-party data processing and retention
data retention and permission scope
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Do not claim hosted endpoint or individual business-domain tools; it proxies another server.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

Supergateway v4.1.0 was released 2026-09-30.

Technical identity

npm/supergateway

Exact implementation source: https://www.npmjs.com/package/supergateway ↗
Reviewed resource type: Gateway
Repository identity: supercorp-ai/supergateway
Package identity: npm:supergateway

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
supercorp-ai/supergateway
Recorded repository material and project history.
Includes references whose attribution is not established.
Package registry ↗
supergateway
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Placeholder URL is illustrative only; never flag as copy-ready configured server.
Install documentation is not a guarantee of current package/runtime compatibility.
MCP transport gateway; does not provide standalone tools. Publisher documents streamable HTTP/SSE/stdio translation and needs a real upstream.
Replace publisher example URL with an upstream endpoint that the user operates or trusts. For HTTP→stdio use supergateway --streamableHttp URL, or --sse for legacy SSE. Inverse direction requires separate stdio server process. Configure TLS and auth appropriately.
After selecting REAL upstream, inspect its tools/list and transport handshake; never test sample example.com as a live endpoint. (Documentation review only, not runtime verified.)
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / configure gateway or CLI
Publisher instructions
Publisher installation/integration method, not a generic MCP server.
Publisher setup example · Publisher instructions · Review before use
```
npx -y supergateway --streamableHttp https://mcp-server.example.com/mcp
```
Configure / authenticate
MCP100 setup guide
Gateway/transport bridge: replace example URL with actual upstream and select --stdio / --sse / --streamableHttp as required; not an independent tool catalog.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Replace publisher example URL with an upstream endpoint that the user operates or trusts. For HTTP→stdio use supergateway --streamableHttp URL, or --sse for legacy SSE. Inverse direction requires separate stdio server process. Configure TLS and auth appropriately.
Check connection
Suggested check
Check gateway startup and target MCP handshake; optional --healthEndpoint supported in stdio to network conversion.
Remove / uninstall / revoke
MCP100 setup guide
This is a gateway / integration component, not a standalone server. Remove the app SDK/package or gateway config using the matching package manager; stop deployed processes separately. For the method installed globally, use `npm uninstall -g supergateway`.
Conditional host / package cleanup · MCP100 composed guide
npm uninstall -g supergateway

Official Documentation & Sources

What it does

MCP transport bridge for stdio, SSE, WebSocket and Streamable HTTP.

Capability: Developer Tools
Resource type: Gateway
Best fit: Deploy or connect MCP servers across different transports

Representative uses

Transport conversion
forwarding and authentication headers
port/network exposure security

Limitations

Do not claim hosted endpoint or individual business-domain tools; it proxies another server.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Transport gateway; downstream server tools and risks inherited. Bind locally and authenticate before public exposure.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: A network-exposed gateway can expose all capabilities of its attached MCP server. Do not bind publicly without independent access controls.

Access scope and cautions

Write actions: Not verified
Risk level: high
Security notes: Advisory/security review not completed; no safety badge.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Transport conversion; forwarding and authentication headers; port/network exposure security.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio, sse, streamable_http, websocket. Client notes: Verify a reachable MCP endpoint and list the downstream tools; no single business-tool contract. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Gateway forwards auth to upstream MCP endpoints; bearer/header flags are configurable; no universal built-in identity policy.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Transport gateway; downstream server tools and risks inherited. Bind locally and authenticate before public exposure.

What limitations and risks should I check before use?

It proxies another server; hosted endpoints and individual business-domain tools are not established by this record. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. Converts local MCP processes to network endpoints; network exposure and downstream tool authority require operator configuration. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.