Skip to main content
Glama
Sign In
luca-network

SPR (Sealed Payment Record)

Official
by luca-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to SPR (Sealed Payment Record)

No user-submitted related servers found.

    Related Servers

    • Parimit

      cad07
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to propose structured payment intents, apply deterministic policy, require human approval, and record tamper-evident audit trails without connecting to live payment rails.
      MIT

    • mcp-audit-gateway

      elang2
      A
      license
      Not graded
      quality
      A
      maintenance
      Tamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.
      3
      18 npm
      MIT

    • wwall

      axdvdv
      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.
      -

    • fidacy-mcp

      lucaslubi
      A
      license
      A
      quality
      C
      maintenance
      Payment firewall for AI agents: a signed, independently verifiable verdict on every money-moving action. Blocks wrong/lookalike payee, over-cap, and duplicate-invoice (BEC) fraud before money moves — anyone can verify a verdict against the public JWKS. Free, local-first, non-custodial.
      12
      1
      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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools occupy clearly distinct steps of the payment lifecycle (declare intent, check, record settlement, verify, cancel), and the three export tools explicitly cross-reference each other ("use export_xbrl_csv instead", "use export_package instead") so their boundaries are spelled out. The only residual overlap is among the three export_* tools, which a careless agent could still misselect, but the descriptions mitigate it well.

    Naming Consistency5/5

    Every name is a snake_case verb_noun phrase (record_intent, cancel_intent, get_intent, check_payment, record_settlement, list_records, verify_record, export_package, export_xbrl_csv, export_dispute_pack). The verb prefixes are used meaningfully and consistently, and multi-word objects like export_xbrl_csv still follow the same predictable pattern.

    Tool Count5/5

    Ten tools is a well-scoped set that maps cleanly onto the domain's stages: intent management (3), settlement (3), and exports (3) plus the pre-payment check. No tool looks redundant or bolted on, and nothing obviously needed is missing from the count.

    Completeness4/5

    The surface covers the full lifecycle: declare/get/cancel intents, check before paying, record settlement, list and verify records, and export for auditors, accounting, or disputes. Minor gaps remain: there is no way to enumerate intents (get_intent needs an ID, and no list_intents exists), and no single-record fetch since list_records returns the entire unpaged book, but agents can work around both via record listings.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources