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/hs737/mcp-server-for-ynabWrote 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/hs737/mcp-server-for-ynab/ynab)<a href="https://agentmods.dev/mcp/hs737/mcp-server-for-ynab/ynab"><img src="https://agentmods.dev/badge/mcp/hs737/mcp-server-for-ynab/ynab/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/hs737/mcp-server-for-ynab/ynab"><img src="https://agentmods.dev/badge/mcp/hs737/mcp-server-for-ynab/ynab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ynab 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
{
"ynab": {
"command": "uvx",
"args": [
"mcp-server-for-ynab==0.4.0",
"stdio"
],
"env": {
"YNAB_API_KEY": "${YNAB_API_KEY}",
"YNAB_PLAN_ID": "${YNAB_PLAN_ID}"
}
}
}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 Changed 3a98536a5f0b
- 1mo ago First seen · 13 lines scan A e6146fa3dbe5
ynab is an MCP server published in the GitHub repository hs737/mcp-server-for-ynab (2 stars, last pushed 2d 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
ynab-budget-mcp
Curated YNAB MCP tools with experimental guarded assignment previews. Runs locally from the ynab-budget-mcp npm package.
pocketsmith-mcp
Production-ready MCP server for PocketSmith personal finance API. Runs locally from the pocketsmith-mcp Python package.
agentpay
MCP server "agentpay" as configured in phuocdu/agentpay-vn. Runs agentpay.mcp_server with python. Needs 2 environment variables to run.
agentpay-vn
VietQR payment infrastructure for AI agents — AgentPay VN MCP server & Python SDK. Runs locally from the agentpay-vn Python package. Needs 2 environment variables to run.
tuskledger-mcp
MCP server for Tusk Ledger — gives your AI assistant typed access to your local personal finance data. Runs locally from the tuskledger-mcp Python package.
edgar-mcp
MCP server for SEC EDGAR financial data with a manifest-backed 31-tool surface. Runs locally from the edgar-mcp Python package.