Is Git tag name safety, name discarded 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.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 41ms20/20
- Tool poisoning30 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/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 Git tag name safety, name discarded does
- GitwandAuto-resolves Git merge conflicts so agents only touch the complex hunks.not reviewedEstablishedA
- PalinodeInspectable, correctable project memory in git-versioned Markdown for AI agents.not reviewedEstablishedC
- SrclightDeep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.not reviewedEstablishedA
Git tag name safety, name discarded reviews, tools and install