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.
/plugin marketplace add oliverames/ynab-mcp-servernpx agentmods add plugins/oliverames/ynab-mcp-server/ynab-mcp-servergit 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/plugins/oliverames/ynab-mcp-server/ynab-mcp-server)<a href="https://agentmods.dev/plugins/oliverames/ynab-mcp-server/ynab-mcp-server"><img src="https://agentmods.dev/badge/plugins/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 3d 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
{
"name": "ynab-mcp-server",
"displayName": "YNAB",
"version": "5.2.0",
"description": "YNAB MCP connector for budgets, transactions, categories, scheduled transactions, accounts, months, payees, and budget review workflows.",
"author": {
"name": "Oliver Ames",
"email": "[email protected]",
"url": "https://github.com/oliverames"
},
"homepage": "https://github.com/oliverames/ynab-mcp-server#readme",
"repository": "https://github.com/oliverames/ynab-mcp-server",
"license": "MIT",
"keywords": [
"mcp",
"ynab",
"budget",
"finance",
"personal-finance"
],
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 23 lines scan A a15bb1377d7f
ynab-mcp-server is a plugin published in the GitHub repository oliverames/ynab-mcp-server (27 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-ops
Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which sheds descriptions…
context-budget
Measure a Claude Code session's fixed startup context payload per item, on the consumer's machine at a pinned, version-stamped binary — including per-tool attribution of the built-in tool pools that /context reports only as lump sums, derived live by A/B bare-name-deny differencing with enforced comparability rules…
computer-use
Operating knowledge for Claude Code's built-in computer-use MCP server — the desktop screen-control surface. /computer-use:diagnose resolves a symptom to a cause instead of retrying: why every screenshot is downscaled to a fixed pixel budget and why zoom (not a bigger display) is the way back to detail, how to read a.
coupling
Iteratively reduces coupling in any repository at any altitude — documents, code modules, applications, or repositories: scans for change-transmitting dependencies typed against a coupling model (strength ladder, connascence, volatility weighting), verifies every finding, applies a budgeted batch of safe…
credo
The mentor framework for Claude Code: a self-contained process layer with per-session modes, a work-item lifecycle with a hard Definition of Done, budget-aware autonomy, visual verification, and safety rules that travel into every subagent.
consulting-toolkit
Multi-agent consulting system with an /engagement orchestration command, an Engagement Manager quality gate, and Research, Finance, Deck, and Due Diligence agents. Includes 17 consulting slash commands, deliverable templates, strategy frameworks, and an 8-tool Financial Intelligence MCP server for real-time financial…