Is J-Link 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 J-Link MCP 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
- 8%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 38 read · 1 create · 8 change · 1 run or deploy
Release history: 2 versions in the registry since 2026-08-28, latest 2026-10-26, typically one every 59 days.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
1 medium
- Code scan45 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 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumeval / new Function used
exec.evalout/mcp/standalone.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON