AgentLedger MCP server
Meter, cap, and block AI agent spend before the provider is charged.
0 stars
Reviews
Write oneNobody has reviewed AgentLedger yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AgentLedger tools (12, 1 write)
write = sends, deletes, buys or postsledger_alertsFreeAlert history for an agent: budget warnings (80% threshold) and spending spikes. Requires a credential: either the agent's own agent_secret or its workspace's workspace_key (same rule as GET /v1/alerts).
ledger_api_docsFreeSelf-serve documentation for AgentLedger — quickstart, MCP tools, REST endpoints, budget caps, error codes, and idempotency usage, as markdown.
ledger_examplesFreeComplete, runnable Python recipe for a common AgentLedger integration pattern.
ledger_list_agentsFreeOwner-only: full cross-tenant listing of every agent ever claimed on this instance, with totals. Requires the operator's admin_secret — this is a portfolio-wide view, not a per-agent report (use ledger_report for that — it requires that agent's agent_secret or its workspace_key).
ledger_reportFreeSpend report for an agent over a rolling window. Returns total spend, breakdown by rail and by service, budget status (ok/warning/exceeded), detected anomalies, and entry count. Requires a credential: either the agent's own agent_secret or its workspace's workspace_key (same rule as GET /v1/report).
ledger_revoke_secretFreeInvalidate an agent_id's agent_secret WITHOUT deleting its spend history. Use when a credential may have leaked, or to stop an agent writing. Subsequent writes to that agent fail with agent_secret_mismatch until you rotate a new secret in. The agent_id stays claimed, so no other workspace can claim it and inherit the ledger. Requires the workspace_key that owns agent_id. Returns {"agent_id", "revoked": True, "_note"}, or {"error", "error_code"}.
ledger_rotate_secretFreeMint a NEW agent_secret for an agent_id your workspace already owns, invalidating the old one. Use this to RECOVER an agent whose secret was lost: the previous credential stops working immediately. Requires the workspace_key that owns agent_id — an agent's own agent_secret cannot rotate itself, because a leaked agent credential must not be able to lock its real owner out. Unlike ledger_track this never claims a new agent_id: an unknown id returns agent_not_claimed. The new secret is returned ONCE. Store it before you drop the response. Returns {"agent_id", "agent_secret", "_note"}, or {"error", "error_code"}.
ledger_set_budgetFreeSet spending caps for an agent. Warns at 80%, blocks spend when exceeded — enforced: a ledger_track call that would cross the cap is rejected. Dollar caps (monthly_cents/daily_cents) and token caps (monthly_tokens/ daily_tokens) are independent dimensions: dollar caps only cover non-"tokens" rails, token caps only cover rail="tokens" bookkeeping rows (tokens_in/tokens_out). Set both if the agent uses both. Monthly cap is required; the rest are optional (0 = no limit). Overwrites any existing budget for the agent. Claiming a brand-new agent_id requires your workspace_key; that first call mints an agent_secret (returned once — save it); later calls for that agent_id must pass the agent_secret back (no workspace_key needed again).
ledger_startwrite actionFreeGet a FREE AgentLedger workspace with no credential and no arguments — the MCP equivalent of opening POST /start in a browser. Call this FIRST if you have no credentials yet. Every other tool here (ledger_track, ledger_set_budget, ledger_report, ledger_alerts) needs a workspace_key or an agent_secret, so a caller arriving with neither must start here or it has nowhere to go. Takes NO arguments on purpose: the goal is zero friction. It returns a `workspace_key` (shown exactly once — it cannot be re-revealed, so store it before continuing) which you then send as `workspace_key` on your first ledger_track for a NEW agent_id. That first write returns the agent's own `agent_secret`, which authenticates every write after it. The free tier includes every rail, enforced budget caps, alerts, reports and the MCP server, capped at 3 agents per workspace. Minting is rate-limited per caller IP, the same limit the human door uses. Prefer to pay? POST /v1/billing/x402 with a wallet-signed payment needs no human and buys 24h of Pro (unlimited agents).
ledger_trackFreeRecord a spend entry for an AI agent on any payment rail, with optional token counts. Claiming a brand-new agent_id requires your workspace_key (get one via x402 at POST /v1/billing/x402 — no human, no login — or at /start). That first call mints an agent_secret and returns it in the response — save it, every later call for that same agent_id must pass it back (no workspace_key needed again) or the write is rejected. Amounts are capped at $100,000/entry and must be >= 0. If a budget is set for this agent, an entry that would cross the monthly/daily cap is blocked, not just logged. Include tokens_in/tokens_out + model on every LLM call so token burn shows up in the /v1/tokens report.
read_skillFreeRead a product skill file by its skill:// URI.
skills_list_toolFreeList this product's skills. Each entry carries the SKILL.md URI, its name and description, verbatim frontmatter, and a per-file sha256 manifest. Read a body with `read_skill`.
Public scan report
scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 543ms20/20
- Tool poisoning12 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Install directly
claude mcp add --transport http agent-ledger https://aiagentscity.com/mcp/
AgentLedger: common questions
- Is AgentLedger MCP server safe?
- Mostly: it is graded B (79/100). Read the AgentLedger safety report
- How do I install AgentLedger?
- It runs remotely at aiagentscity.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does AgentLedger need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is AgentLedger maintained?
- The last commit was in the last day (2026-09-19). The latest release is v0.4.1.
- What can I use instead of AgentLedger?
- Servers from other publishers that do the same job: BackBond Agent Scan MCP server, MCP server and Projectmem MCP server. Compare all AgentLedger alternatives.
Alternatives to AgentLedger
Same job from other publishers: the closest match first, then the best rated.
BackBond Agent ScanVet MCP tool manifests before attachment; returns block, review, or no blocking finding.not reviewedGrowingA- MCPAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- ProjectmemCoding agent memory — one local MCP server for every project. Warns before repeating failed fixes.not reviewedGrowingA
- Kosha Model DiscoveryTells your agent which model to use and what it costs, across 45 providers and local runtimes.not reviewedGrowingB
- mcpmMCP security guard + package manager: trust-scored installs, blocks prompt injection and rug-pulls.not reviewedGrowingB