io.github.icohangar-ops/chp-mcp
NPM · @CUBICZAN/CHP-MCP
Spend approval gate for AI agents: budget caps, HITL thresholds, signed audit hash.
Available components
Last scanned (6 hours ago)
Scores higher than 53% of npm servers
Category Finance and Payments
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 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 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 256 tokens (~64/item across 4 items; 4 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 Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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 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.
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.90 → pass security
- 15 Oct 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.
- 14 Oct 26 −3
- Stability: pass → 0.83 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 +2
- Security disclosure: fail → unverified ▼ functional
- 7 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 3 Oct 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.
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 24 Oct 2026 · Analysed npm/@cubiczan/chp-mcp@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
approve_spend ~81
Human-in-the-loop approval for a proposal that returned HITL_REQUIRED. Cannot approve BLOCKED / hard-rule failures (spec §6.3 / §6.5).
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | – |
| approver | string | yes | Human approver identity (email or handle) |
| committed_today | number | – | – |
| policy | object | yes | – |
No output schema declared.
No examples provided.
chp_content_hash ~53
SHA-256 over float-aware canonical JSON (CHP §3.1) — matches Python consensus-hardening-protocol digests for the same object.
| Name | Type | Req | Description |
|---|---|---|---|
| value | – | – | JSON-serializable value to hash |
No output schema declared.
No examples provided.
chp_version ~19
Report MCP server and CHP Profile B protocol versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evaluate_spend_gate ~103
Run CHP Profile B capital/spend gate on a proposed action. Returns LOCKED, HITL_REQUIRED, or BLOCKED with claims and a content hash. Hard policy violations cannot be overridden by a human.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | Proposed trade / spend / mandate action |
| committed_today | number | – | Notional already committed today toward daily_cap (default 0) |
| policy | object | yes | Gate policy (limits, HITL threshold, confidence floor) |
No output schema declared.
No examples provided.
How do I install the io.github.icohangar-ops/chp-mcp server?
io.github.icohangar-ops/chp-mcp runs locally as an npm package, launched with npx -y @cubiczan/chp-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 · @cubiczan/chp-mcp
claude mcp add icohangar-ops-chp-mcp -- npx -y @cubiczan/chp-mcp
What is the io.github.icohangar-ops/chp-mcp server?
io.github.icohangar-ops/chp-mcp is listed in the public MCP registry as io.github.icohangar-ops/chp-mcp. Spend approval gate for AI agents: budget caps, HITL thresholds, signed audit hash. This page covers its npm package (@cubiczan/chp-mcp).
Is the io.github.icohangar-ops/chp-mcp server safe to use?
io.github.icohangar-ops/chp-mcp scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 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.icohangar-ops/chp-mcp server expose?
io.github.icohangar-ops/chp-mcp exposes 4 tools: evaluate_spend_gate, approve_spend, chp_content_hash, chp_version. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.
Is the io.github.icohangar-ops/chp-mcp server still maintained?
io.github.icohangar-ops/chp-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 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.icohangar-ops/chp-mcp server under?
io.github.icohangar-ops/chp-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.