MCP.Market

Gvnr MCP server

online · 100% uptime
by gvnr.dev·dev.gvnr/gvnr·v1.8.1

Budget & cost control for AI agents — per-agent spend caps + rate limits before each call.

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Gvnr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Gvnr tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 274ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 108 days ago8/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace5/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Gvnr compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 37% of 4,460 AI and agents servers
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
468 ms
faster than 29% of 2,331 AI and agents servers

Install Gvnr in Claude Code, Cursor or VS Code

claude mcp add --transport http gvnr https://gvnr.dev/mcp
Add to Cursor

What the publisher says

From the Gvnr repository's README, as published. We do not edit it. Read it on GitHub

Gvnr

Spend caps, rate coordination, idempotency, and a human-in-the-loop gate for AI agents — enforced before the call, not after the invoice. One MCP endpoint, settled via x402 (USDC on Base). No proxy, no self-hosting, no infrastructure to deploy.

Listed on the Official MCP Registry as dev.gvnr/gvnr.

The problem

Agents cost 10–12× more than estimated in production. System prompts, retry loops, and tool calls multiply fast — a runaway agent can generate a $47,000 bill in 11 days. The usual fix, self-hosting a gateway like LiteLLM, means running infrastructure most developers won't set up.

Gvnr is the hosted alternative: an external authority your agent checks before it spends. Your agent asks "am I clear to make this call?" and acts on the answer.

How it works

Gvnr is not an LLM proxy — your tokens never pass through it, and you pay your model provider directly. Gvnr governs the decision to spend, in two independent meters:

1. The governance-operation quota — what you buy from Gvnr. Your account holds a balance of governance operations (operationsremaining). One budgetclear burns one op. You top this up with USDC; it's decoupled from your LLM spend. get_balance reports it.

2. The spend envelope — a USD cap you set, per agent. setenvelope(agentid, limit_usd, window) gives an agent a daily or per-session USD ceiling. Gvnr tracks estimated spend against it and denies once it's exceeded — this is the runaway guardrail. No dollars move; it's an accounting limit you control.

A budgetclear is approved only when both** hold: the account has ops left in the quota, and the agent is under its envelope. The loop:

  1. Your agent calls budgetclear(agentid, model, estimated_tokens) before each LLM request.
  2. Gvnr checks the op quota and the agent's envelope, and returns { approved: true, ... } or { approved: false, reason }.
  3. If denied, your agent skips (or escalates via request_approval).
  4. After the LLM responds, call reconcile(...) with the real token counts so the envelope tracks actual cost, not the estimate.

Quick start

1. Provision an account

curl -X POST https://gvnr.dev/v1/account
# { "api_key": "bg_...", "account_id": "...", "operations_remaining": 25 }

New accounts include 25 free trial ops — enough to run the full loop (set an envelope, budgetclear, reconcile) before you fund anything. Your apikey is the credential for every call; accountid is just an internal reference for support. Account creation is credential-only by design (agent-native) — email is optional**, set separately via POST /v1/account/notification-email, and used only for human approval notices.

2. Top up your governance-op quota

Pay-as-you-go: 1,000 ops per $1, any amount (try the whole rail for $1), USDC on Base. Open the pay page, name your amount, and pass your API key:

https://gvnr.dev/pay?usd=1&api_key=bg_YOUR_KEY

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Gvnr: common questions

Is Gvnr MCP server safe?
Mostly: it is graded B (70/100). Read the Gvnr safety report
How do I install Gvnr?
It runs remotely at gvnr.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Gvnr need an API key?
Yes. The registry entry asks for Authorization.
Is Gvnr maintained?
The last commit was 146 days ago (2026-06-11). The latest release is v1.8.1.
Is Gvnr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Gvnr?
Servers from other publishers that do the same job: Ausca MCP server, agent-device MCP server and agent-device MCP server.
How does Gvnr compare with other AI and agents MCP servers?
safety score 70/100 (higher than 37% of 4,460 AI and agents servers); uptime 100% (of our recent checks; the typical remote AI and agents server answers 100%); response time 468 ms (faster than 29% of 2,331 AI and agents servers). Full comparison.

Alternatives to Gvnr

Same job from other publishers: the closest match first, then the best rated.

  • Ausca
    Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.
    A
  • agent-device
    Let AI agents inspect, control, and debug real iOS, Android, desktop, and TV apps
    A
  • agent-device
    Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
    A
  • Decionis
    Authorize consequential AI agent actions before execution
    A
  • DCC-MCP Core
    Agent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.
    A