GopherHole Agent Hub
NPM · @GOPHERHOLE/MCP · SCANNED SEP 20
Standards-based A2A hub. One MCP connection to thousands of agents, with shared persistent memory.
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 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
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 131 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
- Tool/resource definitions use about 4337 tokens (~76/item across 57 items; 57 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_message" implies "send" 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 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the GopherHole Agent Hub MCP server?
GopherHole Agent Hub runs locally as an npm package, launched with npx -y @gopherhole/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @gopherhole/mcp
claude mcp add helixdata-gopherhole -- npx -y @gopherhole/mcp
{
"mcpServers": {
"helixdata-gopherhole": {
"command": "npx",
"args": [
"-y",
"@gopherhole/mcp"
]
}
}
} {
"servers": {
"helixdata-gopherhole": {
"command": "npx",
"args": [
"-y",
"@gopherhole/mcp"
]
}
}
} codex mcp add helixdata-gopherhole -- npx -y @gopherhole/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"helixdata-gopherhole": {
"type": "local",
"command": [
"npx",
"-y",
"@gopherhole/mcp"
],
"enabled": true
}
}
} openclaw mcp add helixdata-gopherhole --command npx --arg -y --arg @gopherhole/mcp
mcp_servers:
helixdata-gopherhole:
command: "npx"
args: ["-y", "@gopherhole/mcp"] {
"McpServers": {
"helixdata-gopherhole": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@gopherhole/mcp"
]
}
}
} assistant mcp add helixdata-gopherhole -t stdio -c npx -a -y @gopherhole/mcp
{
"mcpServers": {
"helixdata-gopherhole": {
"command": "npx",
"args": [
"-y",
"@gopherhole/mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 13 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
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/@gopherhole/mcp@0.11.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
workspace_forget ~57
Delete memories from a workspace by ID or semantic query.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Specific memory ID to delete |
| query | string | – | Or delete memories matching this query |
| workspace_id | string | yes | ID of the workspace |
No output schema declared.
No examples provided.
workspace_list ~28
List workspaces you are a member of. Workspaces are shared memory spaces for multi-agent collaboration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
workspace_members_add ~62
Add an agent to a workspace (requires admin role).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | ID of the agent to add |
| role | string | – | Role for the new member (default: write) |
| workspace_id | string | yes | ID of the workspace |
No output schema declared.
No examples provided.
workspace_members_list ~27
List members of a workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | yes | ID of the workspace |
No output schema declared.
No examples provided.
workspace_memories ~56
List all memories in a workspace (non-semantic browse).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results (default: 20) |
| offset | number | – | Pagination offset |
| workspace_id | string | yes | ID of the workspace |
No output schema declared.
No examples provided.
workspace_query ~70
Search workspace memories using semantic search. Returns memories matching your query.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results to return (default: 10) |
| query | string | yes | Search query |
| type | string | – | Optional filter by memory type |
| workspace_id | string | yes | ID of the workspace |
No output schema declared.
No examples provided.
workspace_store ~72
Store a memory in a shared workspace. Other workspace members can query this memory.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content to store |
| tags | array | – | Optional tags for categorization |
| type | string | – | Type of memory (default: fact) |
| workspace_id | string | yes | ID of the workspace |
No output schema declared.
No examples provided.
What is the GopherHole Agent Hub MCP server?
GopherHole Agent Hub is an MCP server listed in the public MCP registry as io.github.helixdata/gopherhole. Standards-based A2A hub. One MCP connection to thousands of agents, with shared persistent memory. This page covers its npm package (@gopherhole/mcp).
Is the GopherHole Agent Hub MCP server safe to use?
GopherHole Agent Hub scores 82 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. 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 GopherHole Agent Hub MCP server expose?
GopherHole Agent Hub exposes 57 tools: memory_store, memory_recall, memory_forget, memory_list, agent_ask, and 52 more. Their descriptions and schemas cost roughly 4,337 tokens of context every time the server is loaded.
Is the GopherHole Agent Hub MCP server still maintained?
GopherHole Agent 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 GopherHole Agent Hub MCP server under?
GopherHole Agent 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.