Skip to main content
Glama
Sign In
Jacksonoseikojo1122

spend-guard

by Jacksonoseikojo1122
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to spend-guard

No user-submitted related servers found.

    Related Servers

    • 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
    • capline-mcp by caplinehq

      capline-mcpofficial

      caplinehq
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to make payments with strict spending limits enforced by signed mandates, preventing unauthorized fund movement beyond predefined caps and allowlists.
      4
      12 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

    • spendnod

      gstack-ds
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables human-in-the-loop authorization for AI agent transactions, allowing real-time approval or denial of purchases based on configurable spending limits, vendor blocklists, daily caps, and category restrictions.
      1
      -

    • Agent Wallet MCP

      GitLoopDesign
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with a prepaid, capped payment method so they can request charges without accessing real accounts. Enforces spending limits, requires human approval for larger transactions, and supports out-of-band approvals via CLI, dashboard, or Telegram.
      MIT
    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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: request_payment initiates a payment, check_payment looks up an existing payment's status, and get_my_limits returns policy/limits information. There is no overlap in action or resource, so an agent can easily choose the right tool.

    Naming Consistency5/5

    All names use consistent snake_case with a clear verb_noun structure: check_payment, request_payment, get_my_limits. The pattern is predictable and readable.

    Tool Count5/5

    Three tools are well-scoped for a narrow spend-guard workflow: initiate, inspect, and retrieve limits. Each tool earns its place, and there is no redundant surface.

    Completeness4/5

    The core lifecycle is covered: request a payment, check its status, and understand policy limits. Minor gaps exist, such as listing all payments or canceling a held payment, but these are workaroundable with the current surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources