registry / record
mcp-server-git
Does mcp-server-git MCP work in Claude Code and Cursor? Throne executed mcp-server-git mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is mcp-server-git mcp safe? Static security scan: no findings under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry mcp-server-git
sealed
- scan id
- 4b8c26537bee47758c638286446e5abf
- target
- uvx mcp-server-git
- sealed at
- 2026-06-16 19:20:43Z
- evidence hash
- sha256:3931965c7144e500a00e637c266aabccb63f70754243fbdfcb02c6633207541a
initialize ok: server mcp-git 1.27.2, negotiated protocolVersion 2025-11-25, capabilities ['experimental', 'tools']
supported: tools/list (12 tools); method not found (tolerated): resources/list, prompts/list
all 12 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=serial): 0 ok, 10 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: git_status:accepted (returned result); git_diff_unstaged:accepted (returned result); git_diff_staged:accepted (returned result); git_diff:accepted (returned result); git_commit:accepted (returned result); unknown_method: error(-32602); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2025-11-25, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1 overlapping git_status calls: max_observed_stable_concurrency=1; all ids answered exactly once, but every call returned an error (tool-level isError result), the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server mcp-git 1.27.2, negotiated protocolVersion 2025-11-25, capabilities ['experimental', 'tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (12 tools); method not found (tolerated): resources/list, prompts/list; notes: connection 2 confirms 12 tools
all 12 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=pipelined): 0 ok, 10 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: git_status:accepted (returned result); git_diff_unstaged:accepted (returned result); git_diff_staged:accepted (returned result); git_diff:accepted (returned result); git_commit:accepted (returned result); unknown_method: error(-32602); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2025-11-25, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1/2/4/6 overlapping git_status calls: max_observed_stable_concurrency=6; all ids answered exactly once, but every call returned an error (tool-level isError result), the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
- target
- uvx mcp-server-git pypi
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 14 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 19:20:43Z
- evidence hash
- sha256:3931965c7144e500a00e637c266aabccb63f70754243fbdfcb02c6633207541a
- valid until
- 2026-09-14
paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/mcp-server-git)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.