stacktrace-mcp@0.1.0
VERIFIED· not startedPublisher claims: "Enables turning pasted or logged crash output from Python, Node, Java, Go, Rust, and .NET into compact root-cause reports, mapping frames onto project code, fingerprinting and comparing traces, explaining exceptions, and redacting secrets over MCP." 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 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.
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-09 and scored it 87/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
for bad in (str(secret), "../secret-outside.txt", "..", "/etc/passwd", "C:\\Windows\\win.ini", "a" * 100_000):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.File "/../../../../../../etc/passwd", line 2, in evil3Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose." exec(open('/etc/passwd').read())\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.File "../../etc/passwd", line 1, in evilFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Whatever a frame claims ('../../etc/passwd', 'C:\\Windows\\...', '/app/src/x.py') can onlyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.run(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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.