Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/icohangar-ops/cubiczan-chpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/icohangar-ops/cubiczan-chp/chp)<a href="https://agentmods.dev/mcp/icohangar-ops/cubiczan-chp/chp"><img src="https://agentmods.dev/badge/mcp/icohangar-ops/cubiczan-chp/chp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/icohangar-ops/cubiczan-chp/chp"><img src="https://agentmods.dev/badge/mcp/icohangar-ops/cubiczan-chp/chp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "chp": { "command": "npx", "args": [ "-y", "@cubiczan/chp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 9 lines scan A 5107677553a9
chp is an MCP server published in the GitHub repository icohangar-ops/cubiczan-chp (0 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
governed-mcp-gateway
HTTP MCP gateway: principal on tools/call + SSE, allowlists, vault rotate, CHP gates. Runs locally from the @cubiczan/governed-mcp-gateway npm package.
agent-conductor
AGENTS.md + skills MCP with CHP R0 gate and adversary decision tools. Runs locally from the @cubiczan/agent-conductor npm package.
chp-mcp
Spend approval gate for AI agents: budget caps, HITL thresholds, signed audit hash. Runs locally from the @cubiczan/chp-mcp npm package.
mcp-server
SEC filings and financial data for AI agents: 46 tools for financials, valuation and supply chains. Runs locally from the @evidinvest/mcp-server npm package. Needs 1 environment variable to run.
tegro-money
MCP server for Tegro.Money — connect Claude, Cursor and other AI tools to the Tegro.Money payment API (balances, shops, orders, payouts, rates). Read-only, secure, your API key never leaves your machine. Runs locally from the @tegroton/tegro-money-mcp npm package. Needs 2 environment variables to run.
tegro-finance-mcp
Model Context Protocol server for the Tegro Finance DEX on TON — let an AI assistant read pools, token prices, swap quotes and liquid-staking (stgTON) rates. Read-only, no keys, no signing. Built on @tegroton/tegro-finance. Runs locally from the @tegroton/tegro-finance-mcp npm package.