
Chp Mcp
io.github.icohangar-opsPublished by GitHub account icohangar-opsv0.1.2Updated Oct 24, 2026
Spend approval gate for AI agents: budget caps, HITL thresholds, signed audit hash.
Overview
Local MCP server that gates AI agent spending and tool calls with budget caps, human-approval thresholds and HMAC-signed receipts plus a chained audit ledger.
- What you can do
- Evaluate spend requests against policy caps, confidence floors and human-approval thresholds, returning locked, HITL-required or blocked outcomes
- Record human approvals or denials and mint signed approval receipts bound to actor, tool, resource, arguments hash and expiry
- Check tool calls against allowlists and receipts, denying on changed arguments, host-bound overrides, expiry, replay or bad signatures
- Request authorization for scoped finance tools and run synthetic equity, treasury and rebalance operations only with a valid receipt
- Inspect the chained deny/authorize/execute audit ledger and compute canonical content hashes
- When to use it
- Use it when an agent can trigger spending or sensitive tool calls and you want a fail-closed gate that requires a human-signed receipt for each specific call, with a durable audit trail of refusals. It suits local Cursor or Claude Code setups that need more than a tool-name allowlist.
- Requirements
- Runs locally over stdio via npx or a global npm install of the package; Node.js is needed. Set CHP_RECEIPT_KEY (or AUDIT_LEDGER_KEY) for signing, and optionally CHP_AUDIT_LEDGER to a JSONL path or :memory:. No accounts or remote endpoints are declared.
Installation
In SourceWeft
- Open Chp Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
35% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts