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/oliverames/ynab-mcp-serverWrote 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/oliverames/ynab-mcp-server/ynab-mcp-server)<a href="https://agentmods.dev/mcp/oliverames/ynab-mcp-server/ynab-mcp-server"><img src="https://agentmods.dev/badge/mcp/oliverames/ynab-mcp-server/ynab-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ynab-mcp-server 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 8d 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-mcp-server": {
"command": "npx",
"args": [
"-y",
"@oliverames/mcp-server-for-ynab@latest"
],
"env": {
"YNAB_API_TOKEN": "${YNAB_API_TOKEN}",
"YNAB_BUDGET_ID": "${YNAB_BUDGET_ID}",
"YNAB_OP_PATH": "${YNAB_OP_PATH}",
"OP_SERVICE_ACCOUNT_TOKEN": "${OP_SERVICE_ACCOUNT_TOKEN}",
"YNAB_ALLOW_WRITES": "1"
}
}
}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.
- 8d ago First seen · 16 lines scan A a877973debae
ynab-mcp-server is an MCP server published in the GitHub repository oliverames/ynab-mcp-server (29 stars, last pushed 4d ago), licensed MIT. 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-30.
Other mcp servers, from other repositories
directory
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers. Remote server at skills.911fund.io.
mcp-office-excel
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 4 environment variables to run.
macbeth
MCP server "macbeth" as configured in wende/macbeth. Runs client/dist/mcp.js with node.
mcp
Schedule and publish social posts to 11 platforms with media, campaigns, analytics and AI captions. Runs locally from the @posteverywhere/mcp npm package. Needs 1 environment variable to run.
myfinance-mcp
Personal finance by conversation: expenses, receipts, statement import, budgets, net worth. Remote server at myfinance-mcp.com.
invoiceflow-mcp
AI-powered invoice automation for MCP. Create invoices, predict late payments, auto-remind, reconcile payments, and track cash flow. Runs locally from the invoiceflow-mcp-server npm package.