← Index

mcp-hub

io.github.ni-c/mcp-hubv0.11.4Docker & Containers

Many stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client

The current version, v0.11.4, was published to the official MCP registry on 2026-09-27. It is distributed as @ni-c/mcp-hub on npm and as the Docker image ghcr.io/ni-c/mcp-hub:0.11.4, filed under Docker & Containers by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using mcp-hub in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-10-05 00:49 UTC
screened 2026-08-30tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-28).

Contracts can change after screening, with no version bump. The gate pins mcp-hub’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for mcp-hub](https://mcpindex.ai/server/io-github-ni-c-mcp-hub) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-ni-c-mcp-hub">Independent trust record for mcp-hub</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-ni-c-mcp-hub)](https://mcpindex.ai/server/io-github-ni-c-mcp-hub)
HTML
<a href="https://mcpindex.ai/server/io-github-ni-c-mcp-hub"><img src="https://mcpindex.ai/api/v1/badge/io-github-ni-c-mcp-hub" alt="mcpindex verdict" height="20" /></a>
Environment variables
CONFIG_PATH

Path to the mcp.json listing the servers to expose, in Claude Code's mcpServers format (default mcp.json in the working directory)

IDLE_TIMEOUT_MINUTES

Minutes of inactivity before a server is put to sleep; 0 starts every server at launch and keeps it running (default 60)

TOOL_CACHE_PATH

Tool snapshots of sleeping servers (default .mcp-hub/tool-cache.json beside the config)

LOG_FILE

Mirror the hub's log lines into this file; stdout carries the protocol, so logging goes to stderr otherwise

EXTERNAL_URL
required

Public base URL exactly as clients see it, e.g. https://mcp.example.net (no path)

PASSWORD_HASH
requiredsecret

bcrypt hash of the OAuth login password (htpasswd -bnBC 10 "" 'pw' | tr -d ':\n')

TRUSTED_PROXIES

Comma-separated IPs/CIDRs of the reverse proxy allowed to set X-Forwarded-* headers

CLIENT_REGISTRATION

Which mechanisms a client may use to obtain a client_id: cimd (Client ID Metadata Documents), dcr (RFC 7591 dynamic registration), or both

CIMD_ALLOWED_ORIGINS

Comma-separated https origins whose client ID metadata documents are accepted, e.g. https://chatgpt.com; unset admits every https origin

PORT

Listen port inside the container

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Docker & Containers