Gitignore Drift Monitor MCP server
Watcher — count uncommitted files in repo, surface dominant drift class. YELLOW >100, RED >250.
D48/100grade D
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Gitignore Drift Monitor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gitignore Drift Monitor tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
no findings
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 139 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 48/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Gitignore Drift Monitor compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 48/100
- higher than 9% of 48,255 servers
Install Gitignore Drift Monitor in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
Gitignore Drift Monitor: common questions
- Is Gitignore Drift Monitor MCP server safe?
- Not recommended: it is graded D (48/100). Read the Gitignore Drift Monitor safety report
- Does Gitignore Drift Monitor need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Gitignore Drift Monitor maintained?
- The last commit was 176 days ago (2026-05-12). The latest release is v0.1.0.