Skip to main content
Glama
PocketQuota

PocketQuota

by ReHowever

Related Servers

Alternatives to PocketQuota

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and their operators to track spending across x402/MPP/API-key rails, set budget caps that warn at 80% and reject over-cap entries, auto-price token usage, and pull spend reports and anomaly alerts — plus request and decide approvals and manage credentials. Also attaches an enforcing proxy so an over-budget provider call is refused before it is ever sent.
      18
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to monitor live token consumption and rate-limit windows across providers and assess whether expensive actions are justified before exhausting quotas, with optional budget guardrails.
      2
      122 PyPI
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      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.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Budget management and cost tracking MCP server for autonomous agents, enabling budget creation, cost recording, spending projections, and alert rules.
      MIT

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target clearly distinct actions or resources, with readable boundaries between recording, reversing, settling, scheduling, and notification handling. Minor potential confusion exists between budget_status and budget_summary, and between budget_adjust_pool and budget_reconcile, though descriptions clarify the different effects.

    Naming Consistency4/5

    All tools use a consistent budget_ prefix and snake_case. Suffixes mix nouns and verbs (budget_status, budget_record, budget_schedules, budget_ack_notification), which is readable but not a strict verb_noun pattern.

    Tool Count5/5

    The 13 tools are well within a manageable range and each appears to serve a distinct budget/quota workflow. The set is neither thin nor bloated for a ledger-style server.

    Completeness4/5

    Core workflows are covered: status, transaction recording/reversal, summaries, reconciliation, scheduling, settlement, and notification acknowledgement. Minor gaps may exist around explicit pool lifecycle management and detailed single-record retrieval, but agents can work around them via existing list and adjustment tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues