Skip to main content
Glama

Related Servers

Alternatives to zshield-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Policy-gated agent spend with signed receipts and rail-extract audit: a fail-closed gate issues a COSE receipt for every allowed payment, and the audit reconciles those receipts against a rail extract so a settlement with no receipt is named rather than assumed. It settles on a mock rail, holding no wallet and signing no transaction.
      5
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to inspect pot balances, deposits, deposit addresses, and spend approvals, and to pay for PaidResources on spark/USDB or send to allowlisted Spark addresses within a per-spend cap. Transactions above the cap become human approval tickets, and the pot key remains in the OS keychain so nothing is signed until approval.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to propose wallet payments while a local, human-authored policy decides whether each transaction is approved, requires human confirmation, or is refused, and records every decision in a signed, append-only ledger.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to manage a Bitcoin wallet and request payments through MCP, while every spend requires a per-payment human approval code and defaults to signet.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets an AI agent propose crypto payments under enforced per-period caps, per-payment limits, and allowed recipients and coins, while holding only a guard token so that a human reviews and signs every draft in their own wallet.
      MIT

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of overlap or misselection between tools. The single tool's purpose—paying shielded ZEC under a spending cap—is singular and unambiguous.

    Naming Consistency5/5

    zcash_pay follows a clear snake_case resource_action pattern. There are no competing conventions to create inconsistency, so the naming is fully predictable for this server.

    Tool Count3/5

    A single tool is very thin for a server named zshield-mcp, which implies broader policy, allow-list, and audit functionality. The pay tool itself is well-scoped, but the overall surface feels under-provisioned.

    Completeness2/5

    The description implies allow-listed recipients, spending caps, and audit logging, yet only the payment action is exposed. There are no tools to inspect the audit log, manage the allow-list, check balances, or query transaction status, leaving significant operational gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues