MCP.so
Sign In
B

Budget Governor MCP Server

@mightbesaad

Basic information

Category

AI & Agents

Transports

stdio

Auth

oauth

Author

mightbesaad

Submitted by

mightbesaad

About Budget Governor MCP Server

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).

#budget#cost-control#spend-cap#rate-limit#ai-agents#idempotency#x402#governance

Budget Governor MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "gvnr": {
      "url": "https://gvnr.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_GVNR_API_KEY"
      }
    }
  }
}

Budget Governor MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Budget Governor?

Budget Governor is a hosted MCP server that enforces spend caps, rate coordination, idempotency, and a human‑in‑the‑loop gate for AI agents – enforced before the LLM call, not after the invoice. It integrates via one MCP endpoint and settles using x402 (USDC on Base). It is built for developers running AI agents who need cost controls without self‑hosting proxy infrastructure.

How to use Budget Governor?

Add the MCP URL https://gvnr.dev/mcp?api_key=bg_YOUR_KEY to any MCP‑compatible client. Provision an account via POST /v1/account (includes 25 free trial ops), top up your governance‑operation quota with USDC, set a spend envelope per agent, then call budget_clear before each LLM request and reconcile after.

Key features of Budget Governor

  • Pre‑call spend clearance against a per‑agent USD envelope
  • Independent governance‑operation quota (1,000 ops per $1 USDC)
  • Per‑(agent, provider, model) rate limiting with retry‑after hint
  • Request‑level idempotency deduplication for retry safety
  • Human‑in‑the‑loop approval flow with polling API
  • No proxy – tokens never pass through the server

Use cases of Budget Governor

  • Prevent runaway agent costs by capping daily or per‑session spend
  • Coordinate request rates across multiple agents sharing a model provider
  • Deduplicate retried LLM calls to avoid double billing
  • Pause execution for human approval on high‑value or sensitive actions
  • Meter and bill agent usage with a pay‑as‑you‑go governance quota

Frequently asked questions

1

What does Budget Governor NOT do?

Budget Governor is not an LLM proxy – your tokens never pass through it, and you pay your model provider directly. It governs only the decision to spend.

2

What are the runtime requirements?

No self‑hosting, infrastructure, or proxy to deploy. It is a hosted endpoint accessible via HTTP.

3

Where does data live?

All state (op quota, envelopes, approvals) is managed server‑side on gvnr.dev infrastructure. Your API key is the credential.

4

What transports and auth are supported?

HTTP with Bearer token (API key) for both REST and MCP. The MCP endpoint uses the URL `https://gvnr.dev/mcp?api_key=bg_YOUR_KEY`.

Comments

More AI & Agents MCP servers