@modelcontextprotocol/server-everything
mcp:npm:@modelcontextprotocol/server-everything · v2.2.1 · sha256:02344cd2d57f · as of 2026-11-09
- Does it take your key? no evidence
- No private-key read found in what we read of its setup and published code — the limits say how much that was.
- No evidence line on file for this question yet.
- Does your key leave? observed
- Not observed — no planted key left during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
- We ran it with planted test keys and saw it.
- Can it move funds on its own? no evidence
- Unknown — we could not read what it exposes.
- No evidence line on file for this question yet.
- What changed? observed
- No change in key, host or fund behaviour since 2.1.0.
- We ran it with planted test keys and saw it.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| modelcontextprotocol.io | code | vendor | traced |
| raw.githubusercontent.com | code | registry | traced |
| registry.npmjs.org | install | registry | observed |
Evidence (3 lines)
- observedO-hosts2026-11-09
registry.npmjs.org was contacted during install (registry).
sandbox:obs_705c89013bc51696
- tracedT-hosts2026-11-09
modelcontextprotocol.io appears in shipped code (vendor).
dist/tools/trigger-url-elicitation.js
- tracedT-hosts2026-11-09
raw.githubusercontent.com appears in shipped code (registry).
dist/tools/gzip-file-as-resource.js
Limits
- Traced analysis follows flows inside one module and one hop across a relative import; a longer chain is not followed.
- Key egress not observed during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
- No tool inventory was available, so fund actions were not read.
- Sandbox: DNS queries made directly by the target are not logged; hosts are recorded from proxied HTTP(S) requests and CONNECTs..
- Sandbox: Code that ignores HTTP(S)_PROXY has no route out of the sandbox, so its attempts are not captured..
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
sato.custody/v1 · custody-3
Maintain this project? Respond to this reading
Loading sign-in…