Skills/npm/mcp-register

mcp-register@0.3.0

VERIFIED· not started

Publisher claims: "Sign and register statements on a Forestrie log, verify receipts, buy grants via x402 within caps" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher forestrie · publishing for 69 daysInstalls 0Last detonated 3 h ago
$claude mcp add mcp-register -- npx -y @forestrie/mcp-register
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
no credential variables read in the code
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @forestrie/mcp-register

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-20 and scored it 87/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 · 11 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
11sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-eXgcoP/task/home/.npm/_logs/2026-11-20T19_18_54_406Z-debug-0.log
11sclaimednot started: dependency install failed (exit 1); the server itself was not observed
11sprocessscript backend runs setup only
11sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagedist/node/cli.js:5 · npx invocation of non-well-known package — may execute untrusted code* `npx -y @forestrie/mcp-register` does.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/node/cli.js:22 · npx invocation of non-well-known package — may execute untrusted code* `globalThis.fetch` — exactly what `npx -y @forestrie/mcp-register` should do.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File permission modification commanddist/node/signer-file.js:130 · File permission modification command — agent changes file ownership/permissionsthrow new KeyFileError(`the ${label} file ${path} is accessible to other users (mode ${(stat.mode & 0o777).toString(8)}); chmod 600 it`);Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandsrc/node/payer.ts:94 · File permission modification command — agent changes file ownership/permissions`the payer key file ${path} is accessible to other users (mode ${(stat.mode & 0o777).toString(8)}); chmod 600 it`,Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/node/cli.ts:5 · npx invocation of non-well-known package — may execute untrusted code* `npx -y @forestrie/mcp-register` does.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File permission modification commandsrc/node/signer-file.ts:175 · File permission modification command — agent changes file ownership/permissions`the ${label} file ${path} is accessible to other users (mode ${(stat.mode & 0o777).toString(8)}); chmod 600 it`,Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commanddist/node/payer.js:54 · File permission modification command — agent changes file ownership/permissionsthrow new PayerError("payer_unavailable", `the payer key file ${path} is accessible to other users (mode ${(stat.mode & 0o777).toString(8)}); chmod 600 it`);Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/node/cli.ts:22 · npx invocation of non-well-known package — may execute untrusted code* `globalThis.fetch` — exactly what `npx -y @forestrie/mcp-register` should do.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈71 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 @forestrie/mcp-register@0.3.0 as of 55 min ago. This is the package itself, not its dependencies.