Is Clocknext 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 Clocknext compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 37% of 48,243 servers
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 15 read · 5 change
Release history: 3 versions in the registry since 2026-09-12, latest 2026-10-01, typically one every 17 days.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
1 medium
- Code scan2 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 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/index.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON