io.github.xiaolai/claude-octopus
NPM · CLAUDE-OCTOPUS · SCANNED SEP 20
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured.
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
- 41 of 108 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 (ISC).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 728 tokens (~145/item across 5 items; 5 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 Management93
- Stability observed for 28 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; "claude_code" 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 5 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 io.github.xiaolai/claude-octopus MCP server?
io.github.xiaolai/claude-octopus runs locally as an npm package, launched with npx -y claude-octopus. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · claude-octopus
claude mcp add xiaolai-claude-octopus -- npx -y claude-octopus
{
"mcpServers": {
"xiaolai-claude-octopus": {
"command": "npx",
"args": [
"-y",
"claude-octopus"
]
}
}
} {
"servers": {
"xiaolai-claude-octopus": {
"command": "npx",
"args": [
"-y",
"claude-octopus"
]
}
}
} codex mcp add xiaolai-claude-octopus -- npx -y claude-octopus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xiaolai-claude-octopus": {
"type": "local",
"command": [
"npx",
"-y",
"claude-octopus"
],
"enabled": true
}
}
} openclaw mcp add xiaolai-claude-octopus --command npx --arg -y --arg claude-octopus
mcp_servers:
xiaolai-claude-octopus:
command: "npx"
args: ["-y", "claude-octopus"] {
"McpServers": {
"xiaolai-claude-octopus": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"claude-octopus"
]
}
}
} assistant mcp add xiaolai-claude-octopus -t stdio -c npx -a -y claude-octopus
{
"mcpServers": {
"xiaolai-claude-octopus": {
"command": "npx",
"args": [
"-y",
"claude-octopus"
]
}
}
} 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.
- 18 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.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 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.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 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 20 Sept 2026 · Analysed npm/claude-octopus@1.1.10
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 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 33 |
| No linked repository | 8 |
| 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 →
claude_code ~293
Send a task to an autonomous Claude Code agent. It reads/writes files, runs shell commands, searches codebases, and handles complex software engineering tasks end-to-end. Returns the result text plus a session_id for follow-ups via claude_code_reply.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalDirs | array | – | Extra directories the agent can access for this invocation |
| cwd | string | – | Working directory (overrides CLAUDE_CWD) |
| disallowedTools | array | – | Additional tools to block (unions with server-level blacklist) |
| effort | string | – | Thinking effort override |
| maxBudgetUsd | number | – | Max spend in USD |
| maxTurns | integer | – | Max conversation turns |
| model | string | – | Model override (e.g. "sonnet", "opus", "haiku") |
| permissionMode | string | – | Permission mode override (can only tighten, never loosen) |
| plugins | array | – | Additional plugin paths to load for this invocation (unions with server-level plugins) |
| prompt | string | yes | Task or question for Claude Code |
| run_id | string | – | Workflow run ID — groups related agent calls into one timeline. Auto-generated if omitted; returned in every response for propagation. |
| systemPrompt | string | – | Additional system prompt (appended to server default) |
| tools | array | – | Restrict available tools to this list (intersects with server-level restriction) |
No output schema declared.
No examples provided.
claude_code_reply ~138
Continue a previous claude_code conversation by session ID. Use this for follow-up questions, iterative refinement, or multi-step workflows that build on prior context.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Working directory override |
| maxBudgetUsd | number | – | Max spend in USD |
| maxTurns | integer | – | Max conversation turns |
| model | string | – | Model override |
| prompt | string | yes | Follow-up instruction or question |
| run_id | string | – | Workflow run ID — pass the same run_id from the original call to keep entries grouped. |
| session_id | string | yes | Session ID from a prior claude_code response |
No output schema declared.
No examples provided.
claude_code_report ~106
Generate a self-contained HTML report of a workflow run. No args: list all runs. run_id: detailed report for that run with agent sequence, cost breakdown, and collapsible transcripts. Save the returned HTML to a file and open in a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| include_transcripts | boolean | – | Include full session transcripts in run reports (default: true, requires session persistence) |
| run_id | string | – | Generate detailed report for this run. Omit to list all runs. |
No output schema declared.
No examples provided.
claude_code_timeline ~92
Query the cross-agent workflow timeline. No args: list all runs. run_id: show one run's agent sequence. session_id: retrieve timeline entry and session metadata. Use claude_code_transcript for full transcripts.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | – | Show all entries for this workflow run, ordered by time |
| session_id | string | – | Retrieve timeline entry and session metadata for a specific session |
No output schema declared.
No examples provided.
claude_code_transcript ~99
Retrieve the full conversation transcript for a session from Claude Code's storage. Returns chronological user/assistant messages. Use session_id from a prior query or timeline lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| include_system | boolean | – | Include system messages (default: false) |
| limit | integer | – | Maximum number of messages to return |
| offset | integer | – | Skip this many messages from the start |
| session_id | string | yes | Session ID to retrieve transcript for |
No output schema declared.
No examples provided.
What is the io.github.xiaolai/claude-octopus MCP server?
io.github.xiaolai/claude-octopus is an MCP server listed in the public MCP registry as io.github.xiaolai/claude-octopus. Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. This page covers its npm package (claude-octopus).
Is the io.github.xiaolai/claude-octopus MCP server safe to use?
io.github.xiaolai/claude-octopus scores 79 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 io.github.xiaolai/claude-octopus MCP server expose?
io.github.xiaolai/claude-octopus exposes 5 tools: claude_code, claude_code_reply, claude_code_timeline, claude_code_transcript, claude_code_report. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.
Is the io.github.xiaolai/claude-octopus MCP server still maintained?
io.github.xiaolai/claude-octopus 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 io.github.xiaolai/claude-octopus MCP server under?
io.github.xiaolai/claude-octopus declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.