Is TraceWeave MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
No critical or high findings in the latest scan.
How TraceWeave compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 3 read · 1 change
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
1 medium
- Code scan67 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 17 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumeval / new Function used
exec.evaltraceweave_mcp-2.0.2/src/slang_connectivity_projector.py: …ang_ast evaluated = expression.eval(slang_ast.EvalContext(context_symbol)) …
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON