# Git Insights (oci · ghcr.io/basitalisandhu/mcp-git-insights) Read-only git statistics for a local repository: log, blame ownership, churn, authors, large files. - Trust score: 49/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-16 ## Components - oci · `ghcr.io/basitalisandhu/mcp-git-insights`: 49/100 (this document), [markdown](https://verifymcp.io/servers/basitalisandhu-mcp-git-insights/ghcr-io-basitalisandhu-mcp-git-insights.md), [page](https://verifymcp.io/servers/basitalisandhu-mcp-git-insights/ghcr-io-basitalisandhu-mcp-git-insights) ## Channel facts - Registry: `oci` - Package: `ghcr.io/basitalisandhu/mcp-git-insights` - Version: `0.2.1` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-16. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 100/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). - Clear OSI-approved license (MIT). - Actively maintained (last published 2 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 1085 tokens (~180/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 91/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 73% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the Git Insights MCP server? Git Insights runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-git-insights:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add basitalisandhu-mcp-git-insights -- docker run --rm -i ghcr.io/basitalisandhu/mcp-git-insights:0.2.1 ``` ### Cursor ```json { "mcpServers": { "basitalisandhu-mcp-git-insights": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-git-insights:0.2.1" ] } } } ``` ### VS Code ```json { "servers": { "basitalisandhu-mcp-git-insights": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-git-insights:0.2.1" ] } } } ``` ### Codex ```bash codex mcp add basitalisandhu-mcp-git-insights -- docker run --rm -i ghcr.io/basitalisandhu/mcp-git-insights:0.2.1 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "basitalisandhu-mcp-git-insights": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-git-insights:0.2.1" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: basitalisandhu-mcp-git-insights: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-git-insights:0.2.1"] ``` ### Netclaw ```json { "McpServers": { "basitalisandhu-mcp-git-insights": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-git-insights:0.2.1" ] } } } ``` ### Other ```json { "mcpServers": { "basitalisandhu-mcp-git-insights": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-git-insights:0.2.1" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-14 (score 49, +29) - [security improvement] Injection markers: unverified → pass - [security] First check of Judged manipulation: pass - [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). - [functional improvement] Tool coverage: unverified → 100 - [functional improvement] MCP protocol: unverified → pass - [functional] First check of Schema quality: fail - [functional] First check of Destructive annotations: pass - [functional] First check of Schema quality: fail - [functional] First check of Schema quality: good - [functional] First check of Tool coverage: 73 ### 2026-10-13 (score 20, 0) - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-10-12 (score 20) First indexed and scored. ## MCP tools (6) ### `repo_summary` (~83 tokens) Summarise a repository Return the repository's top-level path, current branch, HEAD commit (hash, author, date, subject), remotes with credential-free URLs, number of commits reachable from HEAD, number of tags and local branches, and the count of modified or untracked files in the work tree. Input parameters: - `repo` (string, required): Path to the repository (any directory inside the work tree). ### `git_log` (~234 tokens) List commits List commits reachable from rev (default HEAD), newest first, with hash, short hash, author name and email, ISO date, subject and (optionally) the files touched. Filters: path, author (substring of name or email), since, until, grep (substring of the message), no_merges. limit is 1 to 500, default 50. Input parameters: - `author` (string) - `grep` (string) - `limit` (integer) - `no_merges` (boolean) - `path` (string): Limit to this file or directory, relative to the repository root. - `repo` (string, required): Path to the repository (any directory inside the work tree). - `rev` (string): Branch, tag, commit or HEAD~n. Default HEAD. - `since` (string): Only commits after this date, in any form git accepts, for example 2026-01-01 or '3 months ago'. - `until` (string): Only commits before this date. - `with_files` (boolean): Include the list of files changed by each commit. Default false. ### `blame_summary` (~133 tokens) Summarise blame for a file Attribute every line of one file at rev (default HEAD) to its last author and return, per author, the number of lines, the percentage, and the most recent commit date; plus the total line count and the number of distinct commits involved. With ignore_whitespace, whitespace-only changes are attributed to the earlier author. Input parameters: - `ignore_whitespace` (boolean) - `path` (string, required): File path relative to the repository root. - `repo` (string, required): Path to the repository (any directory inside the work tree). - `rev` (string): Branch, tag, commit or HEAD~n. Default HEAD. ### `churn` (~207 tokens) Files changed most often Rank files by how many commits touched them, with lines added and removed, over the commits reachable from rev (default HEAD) and optionally limited by since, until and path. Renames are followed and reported under the newest name. Binary files count commits but not lines. limit is 1 to 200, default 25. Also returns the number of commits examined. Input parameters: - `limit` (integer) - `max_commits` (integer): Cap on commits examined. Default 5000. - `path` (string): Limit to this file or directory, relative to the repository root. - `repo` (string, required): Path to the repository (any directory inside the work tree). - `rev` (string): Branch, tag, commit or HEAD~n. Default HEAD. - `since` (string): Only commits after this date, in any form git accepts, for example 2026-01-01 or '3 months ago'. - `until` (string): Only commits before this date. ### `authors` (~176 tokens) Commits per author Count commits per author (grouped by email) over the commits reachable from rev (default HEAD), optionally limited by since, until and path, with each author's first and last commit dates. Merge commits are excluded unless include_merges is true. Input parameters: - `include_merges` (boolean) - `limit` (integer): Default 50. - `path` (string): Limit to this file or directory, relative to the repository root. - `repo` (string, required): Path to the repository (any directory inside the work tree). - `rev` (string): Branch, tag, commit or HEAD~n. Default HEAD. - `since` (string): Only commits after this date, in any form git accepts, for example 2026-01-01 or '3 months ago'. - `until` (string): Only commits before this date. ### `large_files` (~146 tokens) Largest files List the largest blobs in the tree at rev (default HEAD) with their paths and sizes in bytes. With include_history, instead scan every object reachable from any ref (git rev-list --objects --all piped to cat-file --batch-check) and report the largest blobs ever committed, including ones no longer in the tree, which is what makes a clone big. limit is 1 to 100, default 20. Input parameters: - `include_history` (boolean) - `limit` (integer) - `repo` (string, required): Path to the repository (any directory inside the work tree). - `rev` (string): Branch, tag, commit or HEAD~n. Default HEAD. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/basitalisandhu-mcp-git-insights/ghcr-io-basitalisandhu-mcp-git-insights#diagnostics ## Score history - 2026-10-16: 49 - 2026-10-15: 49 - 2026-10-14: 49 - 2026-10-13: 20 - 2026-10-12: 20 ## Common questions ### What is the Git Insights MCP server? Git Insights is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-git-insights. Read-only git statistics for a local repository: log, blame ownership, churn, authors, large files. This page covers its container image (ghcr.io/basitalisandhu/mcp-git-insights). ### Is the Git Insights MCP server safe to use? Git Insights scores 49 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Git Insights MCP server expose? Git Insights exposes 6 tools: repo_summary, git_log, blame_summary, churn, authors, large_files. Their descriptions and schemas cost roughly 979 tokens of context every time the server is loaded. ### Is the Git Insights MCP server still maintained? Git Insights is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the Git Insights MCP server under? Git Insights declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - GitHub Container Registry: https://ghcr.io/basitalisandhu/mcp-git-insights - Repository: https://github.com/basitalisandhu/dev-mcp-servers - Website: https://basitalisandhu.github.io/dev-mcp-servers/ - Changelog RSS feed: https://verifymcp.io/servers/basitalisandhu-mcp-git-insights/ghcr-io-basitalisandhu-mcp-git-insights.xml - Changelog JSON feed: https://verifymcp.io/servers/basitalisandhu-mcp-git-insights/ghcr-io-basitalisandhu-mcp-git-insights.json - HTML version of this page: https://verifymcp.io/servers/basitalisandhu-mcp-git-insights/ghcr-io-basitalisandhu-mcp-git-insights