AgentGuard MCP server
io.github.MerchantGuard/agentguard·v0.3.1Local spend caps, kill-switch blocking and Ed25519-signed receipts for AI agent tool calls.
0 stars71 downloads/wk
Reviews
Write oneNobody has reviewed AgentGuard yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AgentGuard tools (6)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
export_receiptsExport the tenant decision ledger, including earlier process runs, as a hash-chained array of signed receipts with a chain verification result. Memory mode exports this process only.
provenance_previewPreview the provenance AgentGuard would attest for a model and endpoint WITHOUT spending: model identity, weights origin country (China-origin families flagged), hosting jurisdiction, retention posture.
set_model_costRegister a cost for a model with no built-in pricing (required for self-hosted models: AgentGuard fails closed on unknown costs). Cents per 1,000 tokens.
spend_decideGate a model call BEFORE it runs. Pass metadata only (model, token counts, endpoint URL), never prompt content. Returns allow/block plus an Ed25519-signed, content-free receipt with model and hosting provenance (weights origin, jurisdiction, retention). Unknown self-hosted models need set_model_cost first (fail-closed).
spend_statusShow the active policy: caps, tenant, enforcement mode, decisions so far this session, and the signer identity.
verify_receiptIndependently verify an AgentGuard signed receipt. Returns valid true/false. Tampering with any signed field makes verification fail.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 26 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How AgentGuard compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 73% of 4,460 AI and agents servers
- Tools
- 6
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 71
- more than 55% of 1,538 AI and agents servers with a package
What its tools let an agent do: 5 read · 1 change
Install AgentGuard in Claude Code, Cursor or VS Code
Runs npx -y @agentguard-run/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add agentguard -- npx -y @agentguard-run/mcp
What the publisher says
From the AgentGuard repository's README, as published. We do not edit it. Read it on GitHub
@agentguard-run/mcp
AgentGuard® as an MCP server: local spend caps and Ed25519-signed provenance receipts for AI agent actions, usable from any Model Context Protocol host (Claude Desktop, Claude Code, Cursor, Cline, or your own agent runtime).
Zero data plane. Tools accept metadata only: model names, token counts, endpoint URLs. Prompts and completions never pass through this server, and their content stays on your machine. Receipts are content-free.
A configured license uses the license and seat service. Optional activation telemetry requires consent and can be disabled with AGENTGUARDNOBEACON=1. Neither path sends prompts, tool content or receipts.
Install
{
"mcpServers": {
"agentguard": {
"command": "npx",
"args": ["-y", "@agentguard-run/mcp"]
}
}
}Optional environment variables:
A signing keypair is generated on first run and persisted to /mcp-signing.json (0600). Signed decisions are appended to //decisions.ndjson, including the public verification key. Exports include prior process runs and new decisions extend the existing chain. Tenant directory names use the spend store's filename normalization. Spend counters remain process-local, as in earlier versions.
All tools accept optional agentid, taskid, and workflowid identifier parameters. spenddecide passes these to the call context, signing them as actor.agentId, actor.taskId, and actor.workflowId; the configured tenant becomes actor.tenantId. Other tools accept these metadata fields without recording a spend decision. Prompts, arbitrary content, credentials, and filesystem paths are rejected as IDs. Existing calls without these parameters keep working.
Tools
- spenddecide**: gate a model call before it runs. Returns allow/block plus a signed, hash-chained receipt recording model identity, weights origin country (China-origin families such as GLM, DeepSeek, Qwen, and Kimi are flagged automatically), hosting jurisdiction, and retention posture. Unrecognized endpoints (vLLM, Ollama, TGI, your own cluster) route as self-hosted: zero retention, your jurisdiction.
- verifyreceipt**: independently verify any receipt. Change one signed byte and verification fails.
- exportreceipts**: export the tenant decision ledger as a verified hash chain, including earlier process runs. Memory mode exports only the current process.
- setmodelcost: register pricing for self-hosted models (AgentGuard fails closed on unknown costs).
- provenancepreview**: see what would be attested for a model/endpoint without spending.
- spendstatus**: active caps, tenant, decision count, signer fingerprint.
Why
When agents move from hosted APIs to self-hosted models, the provider's spend dashboard, rate limits, and audit logs disappear with the provider. AgentGuard puts them back, locally, and adds something hosted providers never gave you: a cryptographic receipt an outsider can verify without trusting you or us.
More: https://agentguard.run/sovereign/ and https://agentguard.run/sovereign/guide/
Verify independently
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
AgentGuard: common questions
- Is AgentGuard MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the AgentGuard safety report
- How do I install AgentGuard?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does AgentGuard need an API key?
- Yes. The registry entry asks for
AGENTGUARD_LICENSE_KEY. - Is AgentGuard maintained?
- The last commit was 28 days ago (2026-10-06). The latest release is v0.3.1.
- What can I use instead of AgentGuard?
- Servers from other publishers that do the same job: Emilia Protocol MCP server, Ausca MCP server and Agoragentic Agent OS MCP server.
- How does AgentGuard compare with other AI and agents MCP servers?
- safety score 85/100 (higher than 73% of 4,460 AI and agents servers); tools 6 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to AgentGuard
Same job from other publishers: the closest match first, then the best rated.
- Emilia ProtocolExact-action approval for consequential agent actions: request, track, and verify signed receipts.not reviewedEstablishedB
- AuscaPay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.not reviewedEstablishedA
Agoragentic Agent OS MCPTriptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.not reviewedEstablishedB- three.ws ProvenanceAppend-only, signed, on-chain-verifiable agent action log — record and audit what agents did.not reviewedEstablishedB
- AttestixAI agent identity, signed credentials, delegated authority and governance evidence.not reviewedEstablishedA