Is Speclock MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highShell command built from a string (injection risk)
How Speclock compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 69/100
- higher than 33% of 48,255 servers
- Tools that change things
- 11%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 47 read · 6 change
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
1 high
- Code scan41 source files scanned13/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 41 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highShell command built from a string (injection risk)
exec.shell-concatsrc/cli/index.js: …`, { cwd: root, stdio: "pipe" }); execSync(`git commit -m "v${newVersion}"`, { cwd: root, stdio: "pipe…
Overall 69/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON