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.
      81 npm
      MIT
    • send21-budget by send21io

      send21-budgetofficial

      send21io
      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

    • Boundra

      gobeyondfj-cmd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to evaluate every payment intent against user-signed, on-chain-anchored policies before money moves, returning allow, deny, or human-approval verdicts. Provides policy versioning, revocation, spend reports, and audit trails through MCP tools that agents cannot alter without the owner's key.
      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

    ActivityInactive
    ResponsivenessNo issues

    Resources