Is Git branch 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 branch name safety, name discarded does
- PreviewDropDeploy any Git branch to a live HTTPS preview URL from your agent. No Dockerfile required.not reviewedNewC
uploads.shHost files from coding agents; stage on a branch and attach to GitHub PRs.not reviewedEstablishedA- GitwandAuto-resolves Git merge conflicts so agents only touch the complex hunks.not reviewedEstablishedA
Git branch name safety, name discarded reviews, tools and install