Skip to main content
Glama
Sign In
spend-guard

spend-guard

by vulinh1704
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to spend-guard

No user-submitted related servers found.

    Related Servers

    • @vapi-network/mcp

      @vapi-network/mcpofficial

      vAPI-Network
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP clients discover x402 APIs, pay for calls from a local non-custodial wallet, and inspect balances and payment receipts.
      11
      Apache 2.0

    • x402-gateway-mcp

      Marysbrain
      A
      license
      A
      quality
      F
      maintenance
      Enables MCP clients to access all endpoints of an x402 gateway by paying real-time microtransactions (USDC on Base) per API call, with automatic tool discovery and spend guardrails.
      23
      52 npm
      MIT
    • halowerk-mcp

      halowerk-mcpofficial

      halowerk
      A
      license
      A
      quality
      F
      maintenance
      Provides access to 70 paid APIs as MCP tools with per-call and session budgets, paying via x402/USDC on Base without requiring an account or login. Includes a built-in allowlist of hosts and safe defaults to prevent unintended payments.
      14
      72 npm
      MIT

    • PayAgent

      Evoarislan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to autonomously pay for metered web APIs on a per-call basis, settling x402 v2 USDC micropayments via EIP-3009 authorization on Base Sepolia without human involvement. Spending is bounded by configurable per-call caps and host restrictions, and exposes tools to fetch paywalled URLs and inspect the agent wallet's address and balance.
      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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: one performs fetch-and-pay, one reports spending state, and one describes policy. There is no overlap in action or resource, so an agent can easily pick the right tool.

    Naming Consistency3/5

    Names are readable but use mixed conventions: pay_and_fetch is verb_and_verb while spending_status and spending_policy are noun phrases. The shared spending_ prefix helps, but the set does not follow a predictable verb_noun pattern.

    Tool Count4/5

    Three tools is slightly thin but well matched to a narrow spend-guard purpose. Each tool earns its place, though a few more operations could be reasonable.

    Completeness4/5

    The surface covers the core lifecycle: paying via fetch, checking budget/status, and reading enforced policy. Minor gaps exist around explicit history or approval workflows, but these are intentionally left to the user dashboard.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources