Skip to main content
Glama
goodmeta

agent-verifier-mcp

by goodmeta

Related Servers

Alternatives to agent-verifier-mcp

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
      A
      quality
      A
      maintenance
      AI-native payment infrastructure that enables AI agents to make purchases, issue virtual cards, and manage spending within delegated budgets and policy controls.
      7
      321 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to track real-time token spend and cost velocity, automatically throttle or freeze execution when budgets are exceeded, and enforce sandbox and safety guardrails.
      7
      MIT
    • 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
    • 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

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'release' and 'refund' could be confused without careful reading of descriptions. However, the descriptions clearly differentiate pre-commit vs. settled.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, e.g., check_budget, create_budget, query_reservation.

    Tool Count5/5

    7 tools cover the essential budget and payment lifecycle without being bloated. Each tool serves a clear role.

    Completeness4/5

    The tool set covers create, check, hold, settle, release, refund, and query operations. Missing update or delete budget, but those are less critical for the core workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive