mcp-server@1.0.82
CAUTION· startup onlyPublisher claims: "Verified npm launcher for the open-source ContextStream Rust MCP server" Observed in sandbox: sends data to pub-68429b9f7857416c9484b75bf1887b96.r2.dev.
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: Caution 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 codeAlso r2.dev — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · contacted pub-68429b9f7857416c9484b75bf1887b96.r2.dev (undeclared)
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Find out what these hosts are first. In the honeypot it contacted pub-68429b9f7857416c9484b75bf1887b96.r2.dev, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.0.81
vet-skills diff mcp-server 1.0.81 1.0.82In the sandbox, this version reached for nothing 1.0.81 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-18 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: sends data to pub-68429b9f7857416c9484b75bf1887b96.r2.dev.
Behavior trace
Honeypot run · 20 s · 2 scenariosStatic findings
...env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.No other findings across 849 lines in 9 files.
Cost to the agent
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 @contextstream/mcp-server@1.0.82 as of 13 min ago. This is the package itself, not its dependencies.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
- Unclaimed publisher≈ +8 on the totalClaim contextstream: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.