Skip to main content
Glama
caplinehq

capline-mcp

Official
by caplinehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to capline-mcp

No user-submitted related servers found.

    Related Servers

    • interlock-mcp

      Mustaqeem-Rafi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to use payment APIs safely by gating every tool call through deterministic mandates, value checks, and an exactly-once ledger, so they cannot pay twice or exceed authorisation.
      35 npm
      MIT

    • Arbor

      advaitgore
      A
      license
      Not graded
      quality
      D
      maintenance
      AgentPay is the authorization layer between an AI agent and real spending. You define the rules — spending caps, allowed merchants, time windows — and every purchase attempt the agent makes is checked against them in real time. Approved transactions go through. Anything outside the mandate is blocked and logged. No more babysitting every agent action. No more runaway charges.
      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.
      -

    • Openterms-mcp

      jstibal
      A
      license
      A
      quality
      C
      maintenance
      Cryptographic proof of consent for AI agents. Sign before you act. Policy engine enforces spending caps, action whitelists, and escalation rules. Independently verifiable by anyone.
      10
      2
      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 4 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping purpose: reading mandate status, creating a mandate, executing payments, and revoking a mandate. No ambiguity for an agent selecting between them.

    Naming Consistency3/5

    The naming pattern is mixed: 'create_mandate' and 'revoke_mandate' use verb_noun, 'mandate_status' is a noun phrase, and 'pay' is a bare verb. While still readable, the conventions are not uniform.

    Tool Count5/5

    Four tools is well-scoped for a mandate-driven payment system. Each tool addresses a distinct lifecycle stage without redundancy or bloat.

    Completeness4/5

    The core lifecycle—create, read, pay, revoke—is covered. A minor gap is the lack of an update mandate tool, but the domain description indicates mandates are set up once, so this is acceptable.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources