whygit
PYPI · WHYGIT
Read-only Git explainer: what state a repo is in, what an error means, and the exact fix.
Available components
Last scanned (17 hours ago)
Scores higher than 84% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Srikarmk/whygit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 338 tokens (~112/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 67
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 4 Nov 2026 · Analysed pypi/whygit@0.1.2
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Srikarmk/whygit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Srikarmk/whygit/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 3341874610 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5413a9c8c07a67249084f561a6482667c978679d2cdd158976e9536746604222 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
diagnose_repo Diagnose a Git repository ~89
Use when a repository seems stuck or broken: lists every problem found (conflicts, rebase in progress, detached HEAD, diverged branch, large or secret files...), most urgent first, each with a plain explanation and the commands for the user to run.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Repository folder (or any folder inside it). Relative paths resolve against the server's working directory; ~ is allowed. |
Structured output declared, but exposes no named fields.
No examples provided.
explain_git_error Explain a Git error message ~87
Use when a git command printed an error (push rejected, authentication failed, unrelated histories, merge conflict...): says what it means and the fix. Pass path to tailor the fix to the repository.
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | The error output from git or GitHub, pasted verbatim. |
| path | – | – | Optional repository folder; when given, the explanation uses its current state. |
Structured output declared, but exposes no named fields.
No examples provided.
explain_state Summarise a Git repository's state ~78
Use for a neutral plain-English summary of a repository: branch, upstream and ahead/behind (as of the last fetch), remotes, staged/changed/untracked files, and any operation in progress.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Repository folder (or any folder inside it). Relative paths resolve against the server's working directory; ~ is allowed. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the whygit MCP server?
whygit runs locally as a PyPI package, launched with uvx whygit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · whygit
claude mcp add srikarmk-whygit -- uvx whygit
What is the whygit MCP server?
whygit is an MCP server listed in the public MCP registry as io.github.Srikarmk/whygit. Read-only Git explainer: what state a repo is in, what an error means, and the exact fix. This page covers its PyPI package (whygit).
Is the whygit MCP server safe to use?
whygit scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 whygit MCP server expose?
whygit exposes 3 tools: diagnose_repo, explain_git_error, explain_state. Their descriptions and schemas cost roughly 254 tokens of context every time the server is loaded.
Is the whygit MCP server still maintained?
whygit is still listed as active in the MCP registry. We last reached this channel on 4 November 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 whygit MCP server under?
whygit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.