Git Insights
OCI · GHCR.IO/BASITALISANDHU/MCP-GIT-INSIGHTS
Read-only git statistics for a local repository: log, blame ownership, churn, authors, large files.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of OCI servers
Category Version Control
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +29
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 13 Oct 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 12 Oct 26 20
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed oci/ghcr.io/basitalisandhu/mcp-git-insights@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | basitalisandhu/dev-mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/basitalisandhu/dev-mcp-servers/.github/workflows/publish-github-packages.yml@refs/tags/v0.2.1 |
| Rekor log index | 3244679414 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:28d2a6a746094dde19ea29197bd37da41396926e0c6a577df29ba324b4d5f49a |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authors Commits per author ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_merges | boolean | – | – |
| limit | integer | – | Default 50. |
| path | string | – | Limit to this file or directory, relative to the repository root. |
| repo | string | yes | 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. |
No output schema declared.
No examples provided.
blame_summary Summarise blame for a file ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ignore_whitespace | boolean | – | – |
| path | string | yes | File path relative to the repository root. |
| repo | string | yes | Path to the repository (any directory inside the work tree). |
| rev | string | – | Branch, tag, commit or HEAD~n. Default HEAD. |
No output schema declared.
No examples provided.
churn Files changed most often ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
git_log List commits ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | – |
| grep | string | – | – |
| limit | integer | – | – |
| no_merges | boolean | – | – |
| path | string | – | Limit to this file or directory, relative to the repository root. |
| repo | string | yes | 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. |
No output schema declared.
No examples provided.
large_files Largest files ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_history | boolean | – | – |
| limit | integer | – | – |
| repo | string | yes | Path to the repository (any directory inside the work tree). |
| rev | string | – | Branch, tag, commit or HEAD~n. Default HEAD. |
No output schema declared.
No examples provided.
repo_summary Summarise a repository ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Path to the repository (any directory inside the work tree). |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/basitalisandhu/mcp-git-insights
claude mcp add basitalisandhu-mcp-git-insights -- docker run --rm -i ghcr.io/basitalisandhu/mcp-git-insights:0.2.1
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.