About this integration
Many stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.11.3
- Package
- @ni-c/mcp-hub
- Last compatibility test
- Not independently tested
Connect your agent
@ni-c/mcp-hubPublisher README and package manifest were reviewed from pinned captures. The package was not installed or executed and no endpoint was tested. Local stdio mode is documented as requiring no hub login, while HTTP mode and child integrations have separate authentication requirements. Child packages must be independently trusted and reviewed.
Capabilities: Aggregate MCP tools, Supervise child servers, Filter exposed tools, Hot-reload server configuration
Connected profiles
Additional details
io.github.ni-c/mcp-hub
Source ↗ · Checked 2026-09-170.11.3
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@ni-c/mcp-hub
Source ↗ · Checked 2026-09-190.11.3
Source ↗ · Checked 2026-09-19Publisher documentation describes an on-demand supervisor that starts stdio and Docker servers when used, sleeps idle servers, restarts failed children with backoff, and can expose the aggregate locally through the mcp-hub --stdio command. This review qualifies that local stdio mode only; it does not claim that the separate HTTP service is authentication-free.
Source ↗ · Checked 2026-09-19The documented local --stdio mode uses neither HTTP password variable and places the trust boundary at the local user. HTTP endpoints instead use OAuth/password or long-lived API tokens, and individual child servers can require their own credentials.
Source ↗ · Checked 2026-09-19The npm artifact provides mcp-hub and mcp-hub-stdio binaries. The reviewed connection is the local mcp-hub --stdio aggregate over stdin/stdout; network endpoints and configured upstream connections are outside this stdio connection classification.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19