Skip to main content
Glama

Related Servers

Alternatives to SpendGate

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Human-in-the-Loop authorization gateway for AI Agents. Securely pause MCP workflows and route high-risk actions to human approvers via Slack or Email.
      36 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables MCP clients to ask permission before an agent acts, returning allow, deny, or ask_human with receipts, and to monitor agent spend, limits, and recent decisions.
      35 npm
      Functional Source , Version 1.1, ALv2 Future
    • A
      license
      B
      quality
      B
      maintenance
      An MCP proxy that enforces declarative YAML spend policies for AI agents using Agentcard, providing attribution and anomaly detection.
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP proxy that lets you approve an AI agent's multi-step plan once, then enforces that plan in code so only the permitted tools, argument limits, call counts, and pinned versions reach the upstream tools. Blocked or out-of-plan calls never reach your systems, and a changed or failed step holds the plan until a human overrides it.
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: score_spend evaluates a payment, get_quota reads remaining free scores, and get_api_key mints a credential. There is no overlap in intent, and the descriptions reinforce the separation.

    Naming Consistency5/5

    All three names follow a consistent verb_noun snake_case pattern (score_spend, get_quota, get_api_key) with a predictable 'get_' prefix for read/creation helpers and a distinct verb for the main action.

    Tool Count4/5

    Three tools is a reasonable, well-scoped set for a focused spend-scoring gate: one action, one quota check, one credential mint. It sits at the low end but every tool earns its place without redundancy.

    Completeness4/5

    The core workflow is covered end-to-end: mint a key, check quota, then score a spend before transacting. Minor gaps exist (no score history/audit or key revocation), but the primary agent lifecycle is complete and workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues