mcptokens@1.2.0
VERIFIED· not startedPublisher claims: "375 tokens in your agent's harness. One MCP tool that counts the tool-definition cost of any other MCP server." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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 the honeypot saw
- 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.
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-11 and scored it 85/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
assert proc.returncode == 0, f"npx --version exited {proc.returncode}"Fix: Pin versions and sources; vendor anything fetched at install time.return subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# On error: close stdin to break server's reader, kill if notFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# Exit code 0 means npx --version ran successfully.Fix: Pin versions and sources; vendor anything fetched at install time.pytest.skip("npx not on PATH")Fix: Pin versions and sources; vendor anything fetched at install time.except Exception as exc: # defensive net: never let an unhandled error kill the serverFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# exit cleanly; if it doesn't, kill it.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 mcptokens@1.2.0 as of 3d ago. This is the package itself, not its dependencies.