Is Gaffer 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 Gaffer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 36% of 48,255 servers
- Tools that change things
- 67%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 1 read · 1 create · 1 run or deploy
Public scan report
scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it
1 medium
- Code scan3 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 qualitystatic API keys via environment variables6/15
- Maintenancelast push 85 days ago12/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/index.js: … "require(", "import ", "import(", "eval(", "new Function", "Function(", "Buff…
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON