io.github.robbhimself-1337/claude-army
NPM · CLAUDE-ARMY
Orchestrate multiple Claude Code agents in parallel from chat
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm servers
Category Developer Tools
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- 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 243 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 419 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "dispatch_task" implies "deploy" 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
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.
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 −1
No change was recorded against any check on this day. Provenance & Transparency went from 45 to 44.
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 25 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/claude-army@0.3.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
cancel_task ~38
Cancel a running Claude Code agent task. Sends SIGTERM to gracefully stop the agent.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task ID to cancel |
No output schema declared.
No examples provided.
check_tasks ~54
Check the status of all deployed Claude Code agents. Shows which tasks are running, completed, or failed. Use this to monitor progress of background agents.
| Name | Type | Req | Description |
|---|---|---|---|
| status_filter | string | – | Filter tasks by status (default: all) |
No output schema declared.
No examples provided.
dispatch_task ~201
Deploy a Claude Code agent to work on a task in a specific project directory. The agent runs autonomously with full Claude Code capabilities including sub-agent spawning, file editing, bash execution, etc. Use this to delegate coding tasks to background agents. IMPORTANT: After dispatching, return to the conversation immediately. Do NOT call check_tasks or get_task_output unless the user explicitly asks for a status update.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Optional model override (e.g. 'opus', 'sonnet'). Defaults to Claude Code's configured model. |
| permission_mode | string | – | Permission mode for the agent. 'acceptEdits' auto-approves file edits. 'bypassPermissions' skips all checks (use carefully). |
| task | string | yes | Clear description of the task for the Claude Code agent to perform |
| working_directory | string | yes | Absolute path to the project directory (e.g. /home/robbhimself/GarbageFire) |
No output schema declared.
No examples provided.
get_task_output ~78
Retrieve the full output from a Claude Code agent task. Use this to see what the agent did, including its reasoning and actions taken.
| Name | Type | Req | Description |
|---|---|---|---|
| tail_lines | number | – | Only return the last N lines of output (useful for long outputs). Default: all output. |
| task_id | string | yes | The task ID to retrieve output for |
No output schema declared.
No examples provided.
purge_tasks ~48
Clear completed/failed tasks from the task list. Optionally clear all tasks (cancels running ones).
| Name | Type | Req | Description |
|---|---|---|---|
| include_running | boolean | – | Also cancel and purge running tasks (default: false) |
No output schema declared.
No examples provided.
How do I install the io.github.robbhimself-1337/claude-army MCP server?
io.github.robbhimself-1337/claude-army runs locally as an npm package, launched with npx -y claude-army. 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-army
claude mcp add robbhimself-1337-claude-army -- npx -y claude-army
What is the io.github.robbhimself-1337/claude-army MCP server?
io.github.robbhimself-1337/claude-army is an MCP server listed in the public MCP registry as io.github.robbhimself-1337/claude-army. Orchestrate multiple Claude Code agents in parallel from chat. This page covers its npm package (claude-army).
Is the io.github.robbhimself-1337/claude-army MCP server safe to use?
io.github.robbhimself-1337/claude-army scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.robbhimself-1337/claude-army MCP server expose?
io.github.robbhimself-1337/claude-army exposes 5 tools: dispatch_task, check_tasks, get_task_output, cancel_task, purge_tasks. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Is the io.github.robbhimself-1337/claude-army MCP server still maintained?
io.github.robbhimself-1337/claude-army is still listed as active in the MCP registry. We last reached this channel on 5 November 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.robbhimself-1337/claude-army MCP server under?
io.github.robbhimself-1337/claude-army declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.