PocketQuota
Related Servers
Alternatives to PocketQuota
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.18MIT
- AlicenseNot gradedqualityCmaintenanceManages token budgets for AI agents, enabling tracking and enforcement of usage limits with built-in EU AI Act compliance.75 PyPIMIT
- AlicenseAqualityBmaintenanceEnables 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.2122 PyPIMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceBudget management and cost tracking MCP server for autonomous agents, enabling budget creation, cost recording, spending projections, and alert rules.MIT
- AlicenseAqualityCmaintenanceSpending limits for AI agents. Create budgets, enforce limits, track spend across x402, cards, MPP, or any payment rail.7Apache 2.0
TDQS
Scored across 13 tools
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.
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.
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.
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.