Is Evals MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How Evals compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
Release history: 4 versions in the registry since 2026-08-22, latest 2026-10-13, typically one every 15 days.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
2 medium
- Code scan38 source files scanned; 38 source files scanned15/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 15 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumeval / new Function used
exec.evaldist/mcp-server/tools/definitions/export-records.tool.js: … lossy), * inspect (Inspect AI), or lm-eval (lm-evaluation-harness). Writes the artif…
- mediumeval / new Function used
exec.evaldist/mcp-server/tools/definitions/export-records.tool.js: … lossy), * inspect (Inspect AI), or lm-eval (lm-evaluation-harness). Writes the artif…
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON