Projects / mcp-git-audit
Audit a whole tree of Git repositories, read-only until an operator says otherwise.
Walks a tree of checkouts and reports branch, working-tree status, ahead and behind counts, and last-commit metadata for each. The walk and the per-repository git calls are split into separate tools, so one cheap filesystem scan can be cached and re-audited many times. Remote and branch mutations exist but stay hidden until an operator raises the access level, and every walked path is validated against a configured allow-list of safe roots.
Public mcp repository · source
The problem
What this is for.
Asking an agent about thirty checkouts means thirty status calls and no overview, and giving it a shell to do that with means giving it the ability to change them. This server reports the state of a whole tree — branch, working-tree status, ahead and behind counts, last commit — and is read-only until someone deliberately says otherwise.
Whose problem
Whether it is yours.
You want this if you keep a wide working set and want an agent able to tell you what is dirty, what is unpushed and what has been abandoned, without handing it the ability to act on any of it.
Capabilities
What it actually does.
- A cheap filesystem scan that finds every repository under the allowed roots, separated from the git calls so it can be cached and re-audited many times.
- A per-repository audit: branch, working-tree status, ahead and behind counts, and last-commit metadata.
- A closer look at one repository, including its diff, when the summary raises a question.
- Fetch, pull, push, commit and remote management, present but hidden until an operator raises the access level.
State
How finished it is.
Public source, not published to any package registry. Clone it, build it, and register the built server with your MCP client. The scan-and-audit split and the access model are the settled parts.
Using it
How to start.
Not yet published to a registry. Clone the repository, build it, and register the built server with your MCP client.
Boundaries
What it deliberately does not do.
Read-only unless an operator says otherwise: the access level defaults to read, and the mutating tools are not registered at all until it is raised. Every walked path is validated against a configured allow-list of safe roots, so it cannot wander. It observes repositories; it governs none of them and knows nothing about the forge they came from.
Authority
What this repository owns.
A read-only-by-default Git observation adapter for wide working sets.
That boundary is deliberate. The ecosystem separates philosophy, engineering discipline, capability semantics, portable standards, and executable behaviour so that none of them can quietly absorb another. The full directory shows where this project sits relative to the rest.
Nearby
Other projects of the same kind.
mcp-ki-kb-fs— Give an agent scoped read and write access to local knowledge-base directories.mcp-housekeeping-claude— Audit and safely clean the filesystem state Claude applications accumulate.mcp-gsuite— Connect an agent to Google Workspace, with outbound mail confined to drafts.mcp-m365— Connect an agent to Outlook and OneDrive through the Microsoft Graph API.
See every public project, or go straight to the released command-line tools.