mcp@2.8.0
VERIFIEDPublisher claims: "Currents MCP server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Started with a decoy CURRENTS_API_KEY; tool list observed. Tool calls with a real credential not tested.- Tested
- server startup with a tagged decoy in CURRENTS_API_KEY · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with a real credential
- Needs
- CURRENTS_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
Before you give it your token
- It will ask for
API_KEY_LINECURRENTS_API_KEYConfiguration, not credentials: CURRENTS_API_URL, CURRENTS_MCP_SURFACE, MCP_PATH- Where it talks to
- currents.dev (its own)Also playwright.dev — 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
- what the tools do when called with a real credential
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names playwright.dev as well as its own vendor. The guard injects API_KEY_LINE, CURRENTS_API_KEY only into requests to currents.dev (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 2.7.0
vet-skills diff mcp 2.7.0 2.8.0This version reaches for something 2.7.0 did not: 1 new tool (currents-list-test-issues) · 6 rewritten tool descriptors (currents-create-evidence-links, currents-create-webhook, currents-get-spec-instance, currents-get-test-evidence, …). Compared from the two recorded runs, not from source.
- New tools
- currents-list-test-issues
- Rewritten tool descriptors
- currents-create-evidence-links, currents-create-webhook, currents-get-spec-instance, currents-get-test-evidence, currents-get-webhook, currents-update-webhook
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) on 2026-11-20 and scored it 87/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 47 s · 2 scenarios · 0 deviationsStatic findings
"build": "tsdown && chmod 755 dist/index.mjs dist/http.mjs",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.…` with write access in the environment. In a project that has the package, run `npx currents`. Elsewhere, run `npx --package @currents/cmd currents`: `npx currents` alone run…Fix: Pin versions and sources; vendor anything fetched at install time.…only the tests you fixed, locally, when the repository allows it — for example `npx playwright test <spec> -g \"<test title>\"`. Do not report the local run to Currents.\n\nW…Fix: Pin versions and sources; vendor anything fetched at install time.…only the tests you fixed, locally, when the repository allows it — for example `npx playwright test <spec> -g \"<test title>\"`. Do not report the local run to Currents.\n\nW…Fix: Pin versions and sources; vendor anything fetched at install time.…identical. The tool returns the text; write it to `.currents-session/before-a11y.txt` yourself (`session start` makes `.currents-session/` ignored by git)\n- `browser_stop_tracing`, without a path\n\n### 3. Attach the files\n\nRun `current…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…identical. The tool returns the text; write it to `.currents-session/before-a11y.txt` yourself (`session start` makes `.currents-session/` ignored by git)\n- `browser_stop_tracing`, without a path\n\n### 3. Attach the files\n\nRun `current…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…` with write access in the environment. In a project that has the package, run `npx currents`. Elsewhere, run `npx --package @currents/cmd currents`: `npx currents` alone run…Fix: Pin versions and sources; vendor anything fetched at install time.…ait request.get('/api/cart/total?coupon=SAVE10');\n const body = await response.json();\n\n await testInfo.attach('evidence-cart-total.json', {\n body: JSON.stringify(body, null, 2),\n contentType: 'application/json',\n });\n\n expect(body…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…ait request.get('/api/cart/total?coupon=SAVE10');\n const body = await response.json();\n\n await testInfo.attach('evidence-cart-total.json', {\n body: JSON.stringify(body, null, 2),\n contentType: 'application/json',\n });\n\n expect(body…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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
Not checked against OSV yet; the weekly check has not reached this version.