Skills/npm/linode-mcp-server

linode-mcp-server@0.4.0

VERIFIED· startup only

Publisher claims: "MCP server for Linode API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher takashito · publishing for 598 daysInstalls 399Last detonated 12 h ago
$claude mcp add linode-mcp-server -- npx -y @takashito/linode-mcp-server
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
LINODE_API_TOKEN
Where it talks to
no vendor host named in the codeAlso linode.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
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 linode.com as well as its own vendor. The guard injects LINODE_API_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @takashito/linode-mcp-server

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-19 and scored it 85/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 · 37 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
16sprocessdependency install exit 0
36sclaimedstartup only: exited (0) before answering · '/tmp/ks-detonate-1MCV6R/task/home/work/acme-api/.claude/skills/linode-mcp-server/dist/index.js' ] } Node.js v22.23.5
36sprocessscript backend runs setup only
36sprocessno install scripts to re-run

Static findings

HIGH
Credential pass-through configurationdist/client/account.d.ts:81 · Credential pass-through configuration — agent relays sensitive credentialsexport interface ProxyTokenRequest {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
HIGH
Credential pass-through configurationdist/client/account.d.ts:85 · Credential pass-through configuration — agent relays sensitive credentialsexport interface ProxyToken {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
HIGH
Access to sensitive file pathsdist/index.js:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Load environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/index.js:31 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Check for token in command line args, then env var, then .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈47 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 @takashito/linode-mcp-server@0.4.0 as of 12 h ago. This is the package itself, not its dependencies.

linode-mcp-server@0.4.0 safety verdict: Verified (startup only) — KillerSkills