Is Gnt MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — HTTP 525
How Gnt compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 45/100
- higher than 8% of 1,113 Developer tools servers
- Uptime
- 0%
- of our recent checks; the typical remote Developer tools server answers 100%
Public scan report
scanner v0.1.10 · 2026-11-06 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: HTTP 5250/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 525
Overall 45/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Safer options for the same job
- argotRead-only context and complete checks against patterns learned from git history. Local; no LLM.not reviewedEstablishedB
- GitComprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.not reviewedEstablishedA
- jevmemShared project rules and memory for AI coding agents: a JEVMEM.md in git, with a command guard.not reviewedEstablishedB
