Is Nodebench MCP server safe?

Probably. Read the findings first.

C66/100grade C

Use with care. Some checks failed or could not be verified.

What to know before installing

How Nodebench compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 66/100; higher than 23% 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: 60 read · 13 create · 14 change · 3 delete · 1 send or post · 9 run or deploy

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

1 high1 medium

Code scan157 source files scanned8/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

mediumeval / new Function usedexec.eval

dist/tools/selfEvalTools.js: …e. Must have: tests (log_test_result) + eval (promote_to_eval) + quality gate (run_qua…

highShell command built from a string (injection risk)exec.shell-concat

dist/tools/uiUxDiveAdvancedTools.js: … === "win32") { execSync(`start "" "${fullUrl}"`, { stdio: "ignore" }); …

Overall 66/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
not reviewed
Widely used
A