Skip to content

feat(git): Add optional tamper-evident execution audit logging via GE… - #4734

Closed
viruswami5511 wants to merge 6 commits into
modelcontextprotocol:mainfrom
viruswami5511:main
Closed

viruswami5511 wants to merge 6 commits into
modelcontextprotocol:mainfrom
viruswami5511:main

Conversation

@viruswami5511

Copy link
Copy Markdown

Summary

This PR adds optional tamper-evident execution audit logging to mcp-server-git via the GIT_MCP_AUDIT_DIR environment variable, implementing the open GEF-SPEC-1.0 standard (RFC 8785 canonicalization + Ed25519 hash chaining).

Why This is Useful

When autonomous AI agents (Claude Desktop, Cursor, Cline) execute Git operations (git_commit, git_reset, git_checkout), users need forensic proof of what actions were taken without relying on mutable logs.

  • 100% Optional & Zero Overhead: If GIT_MCP_AUDIT_DIR is not set or guardclaw is not installed, the server operates with zero overhead and zero forced dependencies.
  • Offline Verifiable: Ledgers can be verified anytime with guardclaw verify <DIR>.

Verification

  • Verified standard execution works with 0 changes when unconfigured.
  • Added test_audit_logging_when_enabled in tests/test_server.py.

@cliffhall cliffhall added the closed-out-of-scope Closed: out of scope here; listings and new servers go to the MCP Registry (#4875) label Oct 20, 2026
@cliffhall

Copy link
Copy Markdown
Member

Thank you for this pull request, and apologies for the long wait for a response.

These servers are reference implementations: they exist to show how each part of MCP is used, not to be general-purpose products, so new features are taken selectively, and this change isn't one the maintainers plan to take. This repository also now accepts issues, not pull requests, from anyone but its maintainers; the policy is in CONTRIBUTING.md.

This is not a judgment on the idea or on you. A server in the MCP Registry may well offer it, and anyone is welcome to build on these servers to do so. If you think we've misread it, please open an issue describing the problem and the expected behavior.

This is part of the backlog triage in #4875.

@cliffhall cliffhall closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

closed-out-of-scope Closed: out of scope here; listings and new servers go to the MCP Registry (#4875)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants