Skip to main content
Glama
icohangar-ops

@cubiczan/chp-mcp

Related Servers

Alternatives to @cubiczan/chp-mcp

Related Servers

  • A
    license
    B
    quality
    B
    maintenance
    Enables MCP clients to enforce CHP Profile B spend gates, issue and verify signed tool-approval receipts, and audit denied or authorized finance actions.
    12
    28 npm
    MIT
  • A
    license
    Not graded
    quality
    F
    maintenance
    Enables MCP clients to ask permission before an agent acts, returning allow, deny, or ask_human with receipts, and to monitor agent spend, limits, and recent decisions.
    0
    Functional Source , Version 1.1, ALv2 Future
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients such as Claude Desktop to request spending permission, search and view products, complete checkouts, and check spending status, while every payment is validated against the user's configured guardrails before it reaches PayPal.
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables an MCP client to ask whether a purchase is affordable and receive an auditable, deterministic YES/NO verdict backed by an append-only ledger, and to attempt a real governed checkout that returns a structured decline without creating a PayPal order when the answer is NO. It surfaces committed-payment headroom and essential-lane exceptions so agents can gate spending before money moves.
    8 npm
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables MCP clients to read campaign and account data freely while routing every write through human-approved plans, with budget caps, drift refusal, undo, and audit logging.
    6
    MIT

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct role: evaluate_spend_gate runs the policy check, approve_spend performs HITL approval, chp_content_hash computes hashes, and chp_version reports versions. No two tools overlap in purpose or could be easily confused.

Naming Consistency4/5

The names are consistent snake_case and mostly follow a verb_noun pattern (evaluate_spend_gate, approve_spend). The chp_ prefixed helpers break that pattern slightly, but the prefix clearly groups utility/version operations, so the overall convention remains predictable.

Tool Count5/5

Four tools is well-scoped for a narrow CHP Profile B protocol surface: gate evaluation, human approval, hashing, and versioning. Each tool earns its place without redundancy or bloat.

Completeness4/5

The core lifecycle is covered: evaluate → approve, with supporting hash and version utilities. A minor gap is the absence of an explicit tool to inspect proposal details, but the described results from evaluate_spend_gate include claims and content hashes, so agents can proceed without major dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues