mcp@68.2.0

VERIFIED· startup only

Publisher claims: "Avallon API MCP server - generated from OpenAPI" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher avallon-labs · publishing for 261 daysInstalls 18,561Last detonated 3d ago
$claude mcp add mcp -- npx -y @avallon-labs/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
AVALLON_ACCESS_TOKENAVALLON_API_KEYConfiguration, not credentials: AVALLON_BASE_URL
Where it talks to
no vendor host named in the codeAlso avallon.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
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 avallon.ai as well as its own vendor. The guard injects AVALLON_ACCESS_TOKEN, AVALLON_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @avallon-labs/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-11 and scored it 95/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 · 26 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.0sprocessdependency install exit 0
26sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-HuScLb/task/home/work/acme-api/.claude/skills/mcp/dist/server-2WLFXTEC.js' } Node.js v22.23.4
26sprocessscript backend runs setup only
26sprocessno install scripts to re-run

Static findings

No findings across 186 lines in 5 files.

Cost to the agent

Instructions loaded
≈47 tok
1 file · 5 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 @avallon-labs/mcp@68.2.0 as of 3d ago. This is the package itself, not its dependencies.