Skills/npm/algorand-mcp

algorand-mcp@4.4.4

VERIFIED· startup only

Publisher claims: "Algorand Model Context Protocol Local Implementation" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher goplausible · publishing for 258 daysInstalls 160Last detonated 4d ago
$claude mcp add algorand-mcp -- npx -y @goplausible/algorand-mcp
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

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
ALGORAND_TOKENConfiguration, not credentials: ALGORAND_LOCALNET_INDEXER_URL, ALGORAND_LOCALNET_URL, BAZAAR_BASE_URL, ITEMS_PER_PAGE
Where it talks to
goplausible.xyz, goplausible.com (its own)Also algonode.cloud, nf.domains, perawallet.app, algorand.co — 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
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names algonode.cloud, nf.domains, perawallet.app, algorand.co as well as its own vendor. The guard injects ALGORAND_TOKEN only into requests to goplausible.xyz (and its subdomains) and refuses the rest.

$vet-skills run --secrets ALGORAND_TOKEN=goplausible.xyz -- npx -y @goplausible/algorand-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; startup only; authenticated tool behavior not tested) on 2026-11-10 and scored it 93/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 · 33 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
12sprocessdependency install exit 0
32sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-qr5DUP/task/home/work/acme-api/.claude/skills/algorand-mcp/dist/tools/transactionManager/accountTransactions.js' } Node.js v22.23.4
32sprocessscript backend runs setup only
32sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:10 · File permission modification command — agent changes file ownership/permissions"build": "tsc && cp -r src/resources/knowledge/taxonomy src/resources/knowledge/taxonomy-categories dist/resources/knowledge/ && chmod +x dist/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

No other findings across 10,708 lines in 81 files.

Cost to the agent

Instructions loaded
≈52 tok
1 file · 81 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 @goplausible/algorand-mcp@4.4.4 as of 4d ago. This is the package itself, not its dependencies.