InnerVault

mcp-hub

Stale Official MCP Registry, io.github.ni-c

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

Open the source (opens github.com) https://github.com/ni-c/mcp-hub

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: PASSWORD_HASH, TOTP_SECRET. Use a key with the least access you can.

What it is

MCP servers from io.github.ni-c.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

@ni-c/mcp-hub@0.12.0

From the server's entry in the official MCP Registry

oci package (streamable-http)

ghcr.io/ni-c/mcp-hub:0.12.0

From the server's entry in the official MCP Registry

Settings it asks for

  • 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 secret required · bcrypt hash of the OAuth login password (htpasswd -bnBC 10 "" 'pw' | tr -d ':\n')
  • TWO_FACTOR · Set to totp to ask for a one-time code from an authenticator app at every sign-in. Default off.
  • TOTP_SECRET secret · Base32 secret the authenticator app was set up with (mcp-hub-admin totp init). Read only when TWO_FACTOR is totp.
  • 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

Related

  1. mcp-hub

    MCP servers

    A centralized manager for Model Context Protocol (MCP) servers with dynamic server management and monitoring

    Stale GitHub, ravitemer 520 ★MITUpdated 12 months ago

    git clone https://github.com/ravitemer/mcp-hub.git
  2. mcphub

    MCP servers

    Self-hosted MCP gateway and control plane for connecting, controlling, and operating MCP servers.

    Indexed GitHub, samanhappy 2,695 ★Apache-2.0Updated today

    git clone https://github.com/samanhappy/mcphub.git
  3. hatago-mcp-hub

    MCP servers

    Unified MCP Hub for managing multiple Model Context Protocol servers

    Stale Official MCP Registry, io.github.himorishige Updated 14 months ago 1 note

    @himorishige/hatago-mcp-hub@0.0.16
  4. pAIchart MCP Hub

    MCP servers

    MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration

    Stale Official MCP Registry, app.paichart Updated 7 months ago 1 note

  5. agent-mcp-hub

    MCP servers

    One MCP server bridging the Codex, Cursor, OpenCode, Claude, and Antigravity CLI agents

    Stale Official MCP Registry, io.github.blackaxgit Updated 47 days ago 1 note

    agent-mcp-hub@0.6.2
  6. Etsy Seller MCP Hub

    MCP servers

    Self-hosted Etsy seller tools for shop listings, orders, inventory and media via MCP.

    Stale Official MCP Registry, io.github.Bl0ck154 Updated 14 days ago 1 note

    etsy-seller-mcp-hub@0.5.0