Skip to main content
Glama
Cubiczan

@cubiczan/chp-mcp

by Cubiczan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @cubiczan/chp-mcp

No user-submitted related servers found.

    Related Servers

    • Agent Runtime Proxy

      DSHCorrectover
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables fail-closed runtime interception of MCP tool calls, blocking denied, verifier-error, or timed-out invocations while forwarding permitted calls with Ed25519 receipts.
      6 npm
      Elastic 2.0

    • MCP Sentinel

      skguskim
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables secure MCP tool execution through a gateway that validates tool metadata, permissions, and integrity, with approval workflows and optional onchain registry verification.
      -

    • contextboundary-gw

      kannanokannan
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.
      Apache 2.0

    • veor

      winterbim
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.
      MIT

    • SentinelMCP

      ateeqdesktop-dot
      A
      license
      Not graded
      quality
      C
      maintenance
      Enforces deterministic security policies as an inline firewall for MCP server tool calls, with AST-based validation, cryptographic audit logging, and CLI-based evaluation and verification.
      MIT

    • toolwrit

      emektor
      A
      license
      Not graded
      quality
      A
      maintenance
      Policy sidecar for any MCP server: deny-by-default tool allowlist with argument rules, call and USD budget caps, and a hash-chained audit log with RFC 3161 timestamps.
      9
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation2/5

    The authorization lifecycle is split across several tools with fuzzy boundaries: evaluate_spend_gate and evaluate_tool_approval both evaluate proposed actions, while approve_spend, issue_approval_receipt, and request_authorization can all produce signed receipts. Detailed descriptions help, but an agent selecting by name alone will struggle to identify the correct phase.

    Naming Consistency4/5

    Most tools follow a clear lowercase verb_noun pattern such as evaluate_spend_gate, place_equity_order, inspect_audit_ledger, and authorize_tool_call. The only deviations are the two chp_* utility tools, chp_content_hash and chp_version, which are consistently prefixed but not verb-led.

    Tool Count4/5

    Twelve tools is within the ideal range for a policy/authorization MCP and the count is not bloated. However, there is some redundancy in the approval and receipt-issuance tools, so a couple of tools could be consolidated without losing functionality.

    Completeness4/5

    The core flow is covered end-to-end: evaluate policy, request/approve authorization, issue and verify receipts, execute scoped reference tools, and inspect the audit ledger. Missing pieces are mostly non-critical, such as explicit receipt revocation or allowlist management, but agents can work around these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources