Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mcp-hub

NPM · @NI-C/MCP-HUB · 2 COMPONENTS · SCANNED SEP 20

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

Available components

npm · @ni-c/mcp-hub 95 oci · ghcr.io/ni-c/mcp-hub:0.11.3 10
+1 this week 95 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 37 of 108 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ni-c/mcp-hub). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 303 tokens (~50/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the mcp-hub server?

mcp-hub runs locally as an npm package, launched with npx -y @ni-c/mcp-hub. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ni-c/mcp-hub

# add to Claude Code
claude mcp add ni-c-mcp-hub -- npx -y @ni-c/mcp-hub
// .cursor/mcp.json
{
  "mcpServers": {
    "ni-c-mcp-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/mcp-hub"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ni-c-mcp-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/mcp-hub"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ni-c-mcp-hub -- npx -y @ni-c/mcp-hub
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ni-c-mcp-hub": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ni-c/mcp-hub"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ni-c-mcp-hub --command npx --arg -y --arg @ni-c/mcp-hub
# ~/.hermes/config.yaml
mcp_servers:
  ni-c-mcp-hub:
    command: "npx"
    args: ["-y", "@ni-c/mcp-hub"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ni-c-mcp-hub": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ni-c/mcp-hub"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ni-c-mcp-hub -t stdio -c npx -a -y @ni-c/mcp-hub
// mcp.json
{
  "mcpServers": {
    "ni-c-mcp-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/mcp-hub"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 −2
    • Stability: pass → 0.90 functional
  • 19 Sept 26 +1
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Sept 26 −14
    • Tool safety: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.73 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.11.2 → 0.11.3 functional
    • Package version: 0.8.0 → 0.11.3 functional
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@ni-c/mcp-hub@0.11.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ni-c/mcp-hub
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ni-c/mcp-hub/.github/workflows/release.yml@refs/tags/v0.11.3
Rekor log index 2806972730
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:d938fdde422651210f2bc233befe689612085e622d98ec3e5c3a0346a2237b6acad5039e606eaca28bc54801c2ae99f1fa2132fdb62d3b7f8ea6296cd

Background: How many MCP packages publish verified provenance →

Dependencies 108 packages
Packages resolved 108
Deprecated 1
Stale 37
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~303 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call_tool ~65

Call a tool on one of the MCP servers. Arguments must match the schema from get_tool_schema.

NameTypeReqDescription
argumentsobject–Tool arguments matching its input schema
serverstringyesServer name from list_servers
toolstringyesTool name from list_tools

No output schema declared.

No examples provided.

get_tool_schema ~53

Get the full description and JSON input schema of one tool, needed to construct arguments for call_tool.

NameTypeReqDescription
serverstringyesServer name from list_servers
toolstringyesTool name from list_tools
NameTypeReqDescription
annotationsobject––
descriptionstringyesThe full description, untruncated.
inputSchemaobjectyesJSON Schema for the arguments of call_tool.
namestringyes–
outputSchemaobject–JSON Schema the structuredContent of a call conforms to; absent if the tool declares none.
serverstringyes–

No examples provided.

list_servers ~54

List all MCP servers available through this hub, with their status. Call this first to see what is available. Servers marked "hidden" serve their tools only via their own endpoint, but wake_server/sleep_server still manage them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
serversarrayyes–

No examples provided.

list_tools ~45

List the tools of one MCP server with one-line descriptions. Use get_tool_schema before calling a tool for the first time.

NameTypeReqDescription
serverstringyesServer name from list_servers
NameTypeReqDescription
serverstringyes–
toolsarrayyes–

No examples provided.

sleep_server ~44

Stop an on-demand server immediately instead of waiting for its idle timeout. It restarts automatically on the next tool call.

NameTypeReqDescription
serverstringyesServer name from list_servers
NameTypeReqDescription
namestringyes–
statusstringyesWhat the hub is currently doing with this server.

No examples provided.

wake_server ~42

Start an on-demand server now so its first tool call is fast. No-op if it is already running.

NameTypeReqDescription
serverstringyesServer name from list_servers
NameTypeReqDescription
namestringyes–
statusstringyesWhat the hub is currently doing with this server.
toolCountintegeryes–

No examples provided.

Common questions

What is the mcp-hub server?

mcp-hub is listed in the public MCP registry as io.github.ni-c/mcp-hub. Many stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client. This page covers its npm package (@ni-c/mcp-hub).

Is the mcp-hub server safe to use?

mcp-hub scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the mcp-hub server expose?

mcp-hub exposes 6 tools: list_servers, list_tools, get_tool_schema, call_tool, wake_server, sleep_server. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.

Is the mcp-hub server still maintained?

mcp-hub is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the mcp-hub server under?

mcp-hub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.