chargehand
NUGET · CHARGEHAND
Runs coding-agent workers on a codebase question; every claim in the answer carries evidence.
Available components
Last scanned (23 hours ago)
Scores higher than 47% of NuGet servers
Category Code Search and Documentation
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 & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 593 tokens (~197/item across 3 items; 3 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.19.9 → 0.19.11 functional
- Package version: 0.19.9 → 0.19.10 functional
- 1 Nov 26 +1
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.19.8 → 0.19.9 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: pass → unverified ▼ functional
- Package version: 0.19.6 → 0.19.8 functional
- Package version: 0.19.6 → 0.19.7 functional
- 29 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 67 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 86 functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.19.4 → 0.19.6 functional
- 28 Oct 26 0
- Package version: 0.19.3 → 0.19.4 functional
- 26 Oct 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.18.1 → 0.19.3 functional
- Package version: 0.18.1 → 0.19.2 functional
- Package version: 0.18.1 → 0.19.1 functional
- Package version: 0.18.1 → 0.19.0 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 4 Nov 2026 · Analysed nuget/Chargehand@0.19.11
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 | red_tar |
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/Egoushka/chargehand |
|---|---|
| Repository type | git |
| Commit | c3baa5dd036ec163754f0a79f5a6e89d61d09f47 |
| Project URL | https://github.com/Egoushka/chargehand |
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 →
orchestrate ~305
Run a request through chargehand: intake turns it into a Task Spec, coding-agent workers (OpenCode or Claude Code) answer it, and the result comes back as result/v1 with evidence for every claim. The arguments are the request/v1 fields themselves: contract_version, text and context at the top level, not wrapped in a "request" object. context.delivery "local" keeps a run on this machine: a writing run leaves a local branch in the repository and nothing is pushed, opened or sent to a forge; the server's profile can force it. context.enhance false keeps the run from the server's prompt enhancer (nothing sent before, nothing reported after); use it for replays of stored prompts.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_blocks | array | – | Caller-owned prompt blocks. Placed in the task block and recorded in prompt_chain. |
| context | object | yes | – |
| contract_version | – | yes | Always the string "request/v1". |
| driven | object | – | A batch of tasks run as driven sessions, one container each, ending in a draft pull request per task (ADR 0039). Needs context.repository and unique task ids; both are checked by the server, not by t… |
| inputs | array | – | Caller-supplied facts. Claims cite them with evidence kind 'input' and locator = id. |
| text | string | yes | The request in natural language. |
Structured output declared, but exposes no named fields.
No examples provided.
repositories ~65
List the repositories this chargehand server can read: for each, the folder name and owner/name that orchestrate's context.repository.path accepts (a GitHub URL works too), the server's path, and the commit and branch it has checked out now, to use as context.repository.commit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
result ~82
Read the result of a chargehand run that an orchestrate call answered with a run id because it was still running. Returns result/v1 once the run finished; before that, waits a while and returns the run's run-status/v1, so call it again.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run id an orchestrate call returned instead of result/v1. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the chargehand MCP server?
chargehand runs locally as a NuGet package, launched with dnx Chargehand@0.19.11 --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 · Chargehand
claude mcp add egoushka-chargehand -- dnx Chargehand@0.19.11 --yes
What is the chargehand MCP server?
chargehand is an MCP server listed in the public MCP registry as io.github.Egoushka/chargehand. Runs coding-agent workers on a codebase question; every claim in the answer carries evidence. This page covers its NuGet package (Chargehand).
Is the chargehand MCP server safe to use?
chargehand scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 chargehand MCP server expose?
chargehand exposes 3 tools: orchestrate, result, repositories. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.
Is the chargehand MCP server still maintained?
chargehand is still listed as active in the MCP registry. We last reached this channel on 4 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 chargehand MCP server under?
chargehand declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.