Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/cnpierrepapi/ledgerline-aiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/cnpierrepapi/ledgerline-ai/ledgerline)<a href="https://agentmods.dev/mcp/cnpierrepapi/ledgerline-ai/ledgerline"><img src="https://agentmods.dev/badge/mcp/cnpierrepapi/ledgerline-ai/ledgerline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/cnpierrepapi/ledgerline-ai/ledgerline"><img src="https://agentmods.dev/badge/mcp/cnpierrepapi/ledgerline-ai/ledgerline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ledgerline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "ledgerline": { "command": "uvx", "args": [ "ledgerline" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 8 lines scan A 71572e0e8138
ledgerline is an MCP server published in the GitHub repository cnpierrepapi/ledgerline-ai (0 stars, last pushed 2mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
monarch-mcp
MCP server for Monarch Money personal finance. Runs locally from the monarch-mcp-jamiew Python package. Needs 4 environment variables to run.
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
nestegg-calculators
90+ pure finance calculators: loans, investing, bonds, options, tax. Stateless, stores nothing. Remote server at nestegg.money.
central-bank-mcp
Official central-bank & tax-authority rates from 100+ sources. No API key needed to start. Runs locally from the @allratestoday/central-bank-mcp npm package. Needs 2 environment variables to run.
oddsrail
MCP server giving AI trading agents access to prediction markets (Polymarket, Kalshi) with on-chain builder-code attribution and trading signals. Runs locally from the oddsrail Python package. Needs 1 environment variable to run.
lemonsqueezy-mcp-server
Lemon Squeezy SDK as MCP server. Give your AI assistant access to payment and subscription data. Runs locally from the lemonsqueezy-mcp-server npm package. Needs 1 environment variable to run.