Skills/npm/mcp-verify

mcp-verify@0.8.1

VERIFIED· not started

Publisher claims: "Verify a SCITT receipt under a trust root you hold — offline, no backend, no key, no network" 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 1 h ago
$claude mcp add mcp-verify -- npx -y @forestrie/mcp-verify
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-verify

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 88/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 · 7 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.2sprocessdependency 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-VR4p5H/task/home/.npm/_logs/2026-11-20T20_40_40_563Z-debug-0.log
7.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
7.2sprocessscript backend runs setup only
7.2sprocessno 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-verify` does.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/node/fixtures.js:7 · npx invocation of non-well-known package — may execute untrusted code* `fixtures`) so `npx @forestrie/mcp-verify demo` and theFix: Pin versions and sources; vendor anything fetched at install time.
AST06
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-verify` does.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File type combined with upload actiondist/node/server.js:299 · File type combined with upload action — agent may exfiltrate local data files…f commits, as raw Forestrie-Grant v0 payload CBOR — rebuilt from golden/manifest.json at read time. verify_grant_receipt's committedGrant input; pair with golden/grant-receipt.cbor, golden/entry-id.txt and golden/grant-gene…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
npx invocation of non-well-known packagesrc/node/fixtures.ts:7 · npx invocation of non-well-known package — may execute untrusted code* `fixtures`) so `npx @forestrie/mcp-verify demo` and theFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagefixtures/PROVENANCE.md:51 · npx invocation of non-well-known package — may execute untrusted codepublished tarball. Here they must **ship**: `npx @forestrie/mcp-verify demo`Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File type combined with upload actionsrc/node/server.ts:420 · File type combined with upload action — agent may exfiltrate local data files…f commits, as raw Forestrie-Grant v0 payload CBOR — rebuilt from golden/manifest.json at read time. verify_grant_receipt's committedGrant input; pair with golden/grant-receipt.cbor, golden/entry-id.txt and golden/grant-gene…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
File type combined with upload actionfixtures/lane-a/PROVENANCE.md:19 · File type combined with upload action — agent may exfiltrate local data files…ge is frozen in `forestrie/mcp-resolve`'s `test/fixtures/chain/logState.46770471.json` and this snapshot is that package's `fetch_accumulator` output over it | These bytes are **FROZEN**. `manifest.json` carries their sha256 and…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

Cost to the agent

Instructions loaded
≈61 tok
1 file · 74 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-verify@0.8.1 as of 55 min ago. This is the package itself, not its dependencies.

mcp-verify@0.8.1 safety verdict: Verified (not started) — KillerSkills