mcp-server-for-ynab@0.4.0
CAUTION· not startedPublisher claims: "An AI-first MCP server for YNAB. Read-only by default, with reversible writes." 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: Caution 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
YNAB_API_KEYConfiguration, not credentials: FASTMCP_HOST, FASTMCP_PORT, YNAB_HISTORY_PATH, YNAB_PLAN_ID- Where it talks to
- no vendor host named in the codeAlso ynab.com, getpostman.com — 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 ynab.com, getpostman.com as well as its own vendor. The guard injects YNAB_API_KEY 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-09 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
print("ERROR: YNAB_API_KEY is not set. Load your .env first.", file=sys.stderr)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."$PYTHON" -m mcp_server_for_ynab.cli.main http --host "$HOST" --port "$PORT" > "$LOG" 2>&1 &Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.from mcp_server_for_ynab.http_client.client import YnabHttpClientFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.print("ERROR: npx not found. Node is required to build the MCPB bundle.", file=sys.stderr)Fix: Pin versions and sources; vendor anything fetched at install time.result = subprocess.run([sys.executable, "-c", script], capture_output=True, text=True, check=True, env=env)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.print("ERROR: YNAB_API_KEY is not set. Load your .env first.", file=sys.stderr)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.[ -n "$SERVER_PID" ] && kill "$SERVER_PID" 2>/dev/nullFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.from mcp_server_for_ynab.http_client.client import YnabHttpClientFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.from mcp_server_for_ynab.http_client.rate_budget import RateBudgetFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# have no clone and so no .env.example to consult. Name the place theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.from mcp_server_for_ynab.http_client.client import YnabHttpClientFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.echo "ERROR: YNAB_API_KEY is not set. Load your .env first." >&2Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 mcp-server-for-ynab@0.4.0 as of 5d ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim hs737: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.