McpHub
NUGET · MCPHUB · SCANNED OCT 2
MCP bridge that folds multiple MCP servers' capabilities into a few fixed tools for AI tools.
Available components
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 52 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 859 tokens (~122/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_mcp_server_config" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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
How do I install the McpHub MCP server?
McpHub runs locally as a NuGet package, launched with dnx McpHub@0.0.1.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · McpHub
claude mcp add john0king-mcphub -- dnx McpHub@0.0.1.1 --yes
{
"mcpServers": {
"john0king-mcphub": {
"command": "dnx",
"args": [
"McpHub@0.0.1.1",
"--yes"
]
}
}
} {
"servers": {
"john0king-mcphub": {
"command": "dnx",
"args": [
"McpHub@0.0.1.1",
"--yes"
]
}
}
} codex mcp add john0king-mcphub -- dnx McpHub@0.0.1.1 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"john0king-mcphub": {
"type": "local",
"command": [
"dnx",
"McpHub@0.0.1.1",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
john0king-mcphub:
command: "dnx"
args: ["McpHub@0.0.1.1", "--yes"] {
"McpServers": {
"john0king-mcphub": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"McpHub@0.0.1.1",
"--yes"
]
}
}
} {
"mcpServers": {
"john0king-mcphub": {
"command": "dnx",
"args": [
"McpHub@0.0.1.1",
"--yes"
]
}
}
} 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.
- 2 Oct 26 −3
- Stability: pass → 0.80 functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 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.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 2 Oct 2026 · Analysed nuget/McpHub@0.0.1.1
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unverified |
Signer
| Signed as | Repository signature, names nuget.org |
|---|---|
| Subject | CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US |
| Issuer | CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US |
| Valid from | 23 Feb 2024 |
| Valid until | 18 May 2027 |
| Service index | https://api.nuget.org/v3/index.json |
| Owners | John0king |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
Registry declarations For information only
What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.
| Repository | https://github.com/John0King/McpHub |
|---|---|
| Repository type | git |
| Commit | 36f0fd06c08e75bf47ea1dbc0ce5763e0cb8b0af |
| Project URL | https://github.com/John0King/McpHub |
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 →
add_mcp_server_config ~185
Add a new MCP server config source at runtime. You can either provide a file path to a JSON config file (which will be watched for changes), or provide inline JSON content with a 'servers' or 'mcpServers' key. Returns the created source's Id and the servers it registered. The new servers will be lazily connected on first use.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string|null | – | A file path to a JSON config file (relative paths resolved against the workspace). Mutually exclusive with 'json'. |
| json | string|null | – | Inline JSON content with a 'servers' or 'mcpServers' key, e.g. {"servers":{"myserver":{"command":"node","args":["server.js"]}}}. Mutually exclusive with 'file'. |
| name | string|null | – | Optional label for an inline source (ignored if 'file' is provided). |
No output schema declared.
No examples provided.
call_mcp_capability ~129
Invoke a specific capability (tool/prompt/resource). Prerequisites: first call list_mcp_capabilities to find the qualified name, then call describe_mcp_capability to learn the required arguments and their types. Pass the qualified name "serverName.capabilityName" (or a resource URI) and arguments as a key-value object.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object|null | – | Arguments to pass to the capability (key-value object). Optional for capabilities that take no arguments. |
| name | string | yes | The qualified name of the capability (serverName.capabilityName) or a resource URI |
No output schema declared.
No examples provided.
describe_mcp_capability ~97
Get the full details of a specific capability, including its input/output JSON schema, argument names/descriptions/required flags, etc. ALWAYS call this BEFORE call_mcp_capability to learn what arguments the capability expects. Provide the qualified name (from list_mcp_capabilities) in the format "serverName.capabilityName".
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The qualified name of the capability, format: serverName.capabilityName |
No output schema declared.
No examples provided.
list_mcp_capabilities ~114
List all available capabilities (tools/prompts/resources) from all upstream MCP servers, returning a CSV table with Kind, QualifiedName, Server, Name, Description, etc. Also shows each server's connection status. This is the FIRST step: use this to discover capabilities, then call describe_mcp_capability to get parameter details before calling call_mcp_capability.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string|null | – | Optional filter by capability kind: "tool", "prompt", "resource". If omitted, all kinds are returned. |
No output schema declared.
No examples provided.
list_mcp_server_configs ~60
List all registered MCP server config sources and their server definitions. Returns each source's Id, name, kind (file/inline), and the list of server configs it provides. Use this to discover source IDs needed for remove_mcp_server_config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_mcp_server_config ~89
Remove an MCP server config source by its Id. This stops the source's file watcher (if any) and disconnects all servers provided by that source. Use list_mcp_server_configs to find the source Id. Returns the removal result including which servers were disconnected.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | The Id of the config source to remove (obtain from list_mcp_server_configs). |
No output schema declared.
No examples provided.
restart_mcp_server ~88
Restart a specific upstream MCP server by name. Use this when a server becomes unresponsive, returns errors, or needs to pick up changes. The server will be disconnected and re-connected with the same configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | yes | The name of the upstream MCP server to restart (the server name prefix in qualified names, e.g. "filesystem" in "filesystem.read_file") |
No output schema declared.
No examples provided.
What is the McpHub MCP server?
McpHub is an MCP server listed in the public MCP registry as io.github.John0King/mcphub. MCP bridge that folds multiple MCP servers' capabilities into a few fixed tools for AI tools. This page covers its NuGet package (McpHub).
Is the McpHub MCP server safe to use?
McpHub scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. It declares no install or post-install scripts. 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 McpHub MCP server expose?
McpHub exposes 7 tools: restart_mcp_server, remove_mcp_server_config, describe_mcp_capability, list_mcp_server_configs, list_mcp_capabilities, and 2 more. Their descriptions and schemas cost roughly 762 tokens of context every time the server is loaded.
Is the McpHub MCP server still maintained?
McpHub is still listed as active in the MCP registry. We last reached this channel on 2 October 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 McpHub MCP server under?
McpHub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.