Skills/PyPI/monzo-mcp

monzo-mcp@1.1.1

VERIFIED· not started

Publisher claims: "Read-only Monzo banking MCP server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher tcoretech · publishing for 234 daysInstalls 112Last detonated 3d ago
$claude mcp add monzo-mcp -- uvx monzo-mcp
WatchReport an issue

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
HAS_KEYRING_TOKENSMONZO_CLIENT_SECRETConfiguration, not credentials: DISPLAY, MONZO_CLIENT_ID, MONZO_REDIRECT_URI, SSH_CLIENT, SSH_CONNECTION, WAYLAND_DISPLAY
Where it talks to
monzo.com (its own)
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. It asks for HAS_KEYRING_TOKENS, MONZO_CLIENT_SECRET and talks to monzo.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets HAS_KEYRING_TOKENS=monzo.com,MONZO_CLIENT_SECRET=monzo.com -- uvx monzo-mcp

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-11 and scored it 91/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 · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedmcp-server/auth.py:108 · Python subprocess execution detectedsubprocess.run(["powershell.exe", "-Command", f"Start-Process '{url}'"], check=True, capture_output=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 1,833 lines in 20 files.

Cost to the agent

Instructions loaded
≈800 tok
1 file · 20 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 monzo-mcp@1.1.1 as of 3d ago. This is the package itself, not its dependencies.