ForgingStack Ration
Related Servers
Alternatives to ForgingStack Ration
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables high-throughput API rate limiting with deterministic token bucket throttling and burst quota management for AI agents.8-
- AlicenseNot gradedqualityDmaintenancePer-agent quota meter for the A2A network, enabling quota checks with USDC settlement on Base L2 via x402 envelopes.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents and MCP-compatible clients to enforce multi-provider token-bucket and sliding-window rate limits, preventing TPM/RPM throttling across LLM APIs with predictive token consumption budgeting.-
- AlicenseAqualityCmaintenanceEnables AI agents to track spending against configurable daily limits, record and undo expenses across daily, flexible, and safety pools, query remaining quota, manage budget rules, and receive quota alerts through a shared ledger. Supports read-only, bookkeeping, and budget-management permission levels.132MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents to apply adaptive token bucket concurrency limits and backoff scheduling to avoid HTTP 429 errors. It provides deterministic rate-limiting permits and structured telemetry through MCP-compatible clients.8-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and multi-agent frameworks to throttle outbound LLM API calls with multi-provider token-bucket and sliding-window limiting, plus predictive token-consumption budgeting to avoid TPM/RPM throttling. It runs deterministically over MCP with zero dependencies, returning rate-limit decisions and telemetry for any client such as Claude Desktop or Cursor.7-
TDQS
Scored across 8 tools
Each tool targets a distinct resource-action pair: pool lifecycle (create/get/list/topup/delete), unit consumption (draw), receipts (get_receipt), and billing (get_credits). The only near-pair, create_pool vs topup_pool, is cleanly separated by creation-vs-augmentation and by cost semantics. No two tools appear interchangeable.
Seven of eight tools follow a consistent snake_case verb_noun pattern (create_pool, get_pool, list_pools, topup_pool, delete_pool, get_credits, get_receipt). The lone bare verb 'draw' breaks the pattern, though its meaning remains obvious.
Eight tools is well within the sweet spot and every tool earns its place: CRUD on pools, the core draw operation, and supporting receipt/credit lookups. No redundancy or filler.
Pool lifecycle is well covered (create, read, list, topup, delete) plus draw and receipt retrieval, with billing visibility via get_credits. Gaps remain: no way to enumerate draws/receipts for a pool (receipts only fetchable by known id) and no way to adjust pool capacity or refill rate after creation.