Is LLM CLI Gateway 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 LLM CLI Gateway compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 68% of 4,461 AI and agents servers
- Tools that change things
- 12%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 23 read · 3 change
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
1 medium
- Code scan95 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 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- mediumeval / new Function used
exec.evalsocket.yml: … compiles JSON Schema validators using `new Function(...)`. # This is ajv's standard code…
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what LLM CLI Gateway does
- REAReverse engineer anything from your terminal or agent with one CLI and MCP server.not reviewedWidely usedA
- Agent-Native ChatMinimal chat-first app with durable threads, actions, and the app-agent loopnot reviewedEstablishedA
- SuperCompressCompress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.not reviewedEstablishedB