Home / MCP registry index / io.github.entradox/agent-ledger
AgentLedger
io.github.entradox/agent-ledger in the official MCP registry.
Endpoint https://aiagentscity.com/mcp/. Source: github.com/entradox/agent-ledger.
The registry describes it as: Meter, cap, and block AI agent spend before the provider is charged.
We read its 18 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ledger_rotate_secret ledger_revoke_secret ledger_track ledger_set_budget ledger_report ledger_proxy_attach ledger_alerts ledger_wait_events ledger_check_spend ledger_request_approval ledger_approvals ledger_approval_decide ledger_price ledger_start ledger_api_docs ledger_examples skills_list_tool read_skill
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-entradox-agent-ledger)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.