ynab-mcp-server@0.9.0
VERIFIED· not startedPublisher claims: "MCP server for interacting with a YNAB plan" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
TYPESAFE_API_KEYYNAB_API_TOKENConfiguration, not credentials: YNAB_AI_CATEGORIZATION, YNAB_AI_TYPICAL_PAYEES, YNAB_BUDGET_ID, YNAB_MCP_ALLOWED_HOSTS, YNAB_MCP_ALLOWED_ORIGINS, YNAB_MCP_HOST, YNAB_PLAN_ID, YNAB_READ_ONLY- Where it talks to
- no vendor host named in the codeAlso typesafe.ai — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names typesafe.ai as well as its own vendor. The guard injects TYPESAFE_API_KEY, YNAB_API_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 12 s · 2 scenarios · 0 deviationsStatic findings
"build": "tsc && chmod +x dist/index.js dist/http.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."ynab-mcp-server-http": "./dist/http.js"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for ynab-mcp-server@0.9.0 as of 24 h ago. This is the package itself, not its dependencies.