agent-token-budget-mcp

Purpose: Controlling and auditing token usage in agentic AI workflows by enforcing session-level spend caps.

Inferred · not functionally tested

Audience: AI developers and compliance teams managing agentic systems

Inferred · not functionally tested

Functions: agents, monitoring

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

agent-token-budget-mcp sits in PulseGate's AI security & guardrails category. Inferred · not functionally tested: It focuses on controlling and auditing token usage in agentic AI workflows by enforcing session-level spend caps. Inferred · not functionally tested: It is built as an open-source project for AI developers and compliance teams managing agentic systems. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It ships for the command line, and it can be self-hosted.

Behind agent-token-budget-mcp is MEOK AI Labs, and it first shipped in 2026. Development happens publicly on GitHub with 17 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include token budget enforcement, signed attestations, and session spend caps. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.