throng
NPM · THRONG-MCP
Hands work to another coding agent over ACP: Claude Code, Codex, OpenCode, Gemini CLI and others
Available components
Last scanned (17 hours ago)
Scores higher than 81% of npm servers
Category AI and Machine Learning
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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to agent-runbooks/throng-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 936 tokens (~156/item across 6 items; 6 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 Management47
- Stability observed for 14 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 8 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.9.0 → 0.9.1 functional
- 7 Nov 26 66
First indexed and scored.
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 21 Nov 2026 · Analysed npm/throng-mcp@0.9.1
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 | agent-runbooks/throng-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/agent-runbooks/throng-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3759476029 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4f9adeff91f322ed19c9f7dd705f2df51dac3fe3f029913bb57f42db576f18ecafedada6565f767ef2b1c0a45ab5b3869bdc59ad7edd20113236a44d2 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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_thronglet ~73
Cancels the session's running turn (session/cancel) and drops its queued messages; a pending wait_thronglet returns the cancelled error. The session is idle afterwards and accepts a new send_message. No-op on an idle session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | session_id from run_thronglet |
No output schema declared.
No examples provided.
list_harnesses ~58
Lists valid agent values for run_thronglet: installed harnesses with their models and effort levels, installed or configured ones that cannot run with the reason, and the server limits. Built-in harnesses that are not installed are not listed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_thronglets ~76
Lists thronglet sessions on this machine: description, agent, cwd, state (running | queued | idle | failed), queue length, accepts_messages (false: send_message to it fails), timestamps and the last error. Live state is this server's; a session run by another throng instance shows what its record says.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_thronglet ~298
Runs an agent of an installed harness (see list_harnesses) on a task in cwd and returns its final message as JSON {session_id, text, stop_reason, usage, duration_s, warnings?}; with schema, structured replaces text. description names the thronglet for listings. With background: true the call returns {session_id, state, queued} as soon as the turn runs; collect the result with wait_thronglet.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | <harness>/<model>[:<effort>], e.g. claude/opus:max, codex/gpt-6-sol:xhigh; valid values: list_harnesses |
| background | boolean | – | Return as soon as the turn is running (or queued behind the session's current turn); collect the result with wait_thronglet |
| cwd | string | yes | Absolute path; the agent works in this tree |
| description | string | yes | What this thronglet is for, in a few words; shown in session listings |
| prompt | string | yes | Task for the agent |
| schema | object | – | JSON Schema (draft-07 or 2020-12) for structured output: the agent ends with a matching JSON value as its final message, returned as `structured` instead of `text` |
| timeout_s | number | – | Wall-clock limit for the run in seconds; default from config (21600) |
No output schema declared.
No examples provided.
send_message ~315
Sends the next message into an earlier session (session_id from run_thronglet) and returns the same JSON as run_thronglet. A message to a session whose turn is still running waits for that turn to end: turns on one session never overlap. With background: true the call returns {session_id, state, queued} as soon as the turn runs; collect the result with wait_thronglet. steer: true interrupts the running turn and delivers this message next; queued messages follow it. A session its harness cannot continue (resume or load) takes no further message, steer included: list_thronglets shows it as accepts_messages: false.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | Return as soon as the turn is running (or queued behind the session's current turn); collect the result with wait_thronglet |
| prompt | string | yes | Next message for the agent |
| schema | object | – | JSON Schema (draft-07 or 2020-12) for structured output: the agent ends with a matching JSON value as its final message, returned as `structured` instead of `text` |
| session_id | string | yes | session_id from run_thronglet |
| steer | boolean | – | Interrupt the running turn (session/cancel) and run this message as the very next turn, ahead of queued messages. The in-flight tool call is aborted; a half-applied edit may remain. |
| timeout_s | number | – | Wall-clock limit for the run in seconds; default from config (21600) |
No output schema declared.
No examples provided.
wait_thronglet ~116
Waits until a session has no running or queued turn and returns the last turn's result: the same JSON as run_thronglet, or its error. With timeout_s elapsed returns {session_id, state, queued} instead. Idempotent: the result is stored with the session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | session_id from run_thronglet |
| timeout_s | number | – | How long to wait in seconds; default from config (21600). Elapsed → the session state, not an error |
No output schema declared.
No examples provided.
How do I install the throng MCP server?
throng runs locally as an npm package, launched with npx -y throng-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 · throng-mcp
claude mcp add agent-runbooks-throng-mcp -- npx -y throng-mcp
What is the throng MCP server?
throng is an MCP server listed in the public MCP registry as io.github.agent-runbooks/throng-mcp. Hands work to another coding agent over ACP: Claude Code, Codex, OpenCode, Gemini CLI and others. This page covers its npm package (throng-mcp).
Is the throng MCP server safe to use?
throng scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 throng MCP server expose?
throng exposes 6 tools: cancel_thronglet, list_harnesses, list_thronglets, run_thronglet, send_message, wait_thronglet. Their descriptions and schemas cost roughly 936 tokens of context every time the server is loaded.
Is the throng MCP server still maintained?
throng is still listed as active in the MCP registry. We last reached this channel on 21 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 throng MCP server under?
throng declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the throng MCP server?
VerifyMCP ran 16 checks on throng, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.