gitpro
PYPI · GITPRO
Read-only checks of which git name, email and SSH key a repository uses, and why.
Available components
Last scanned (2 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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 5 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Yantrakar/gitpro). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1670 tokens (~98/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
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.
- 17 Oct 26 +16
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 78 → 98 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.4 → 0.4.0 functional
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Oct 26 80
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 17 Oct 2026 · Analysed pypi/gitpro@0.4.0
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 | Yantrakar/gitpro |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Yantrakar/gitpro/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 3285890493 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:47d88962d4f3c418cb1cdb4ead3da290f87596101ebdb5137c7fb07c8458d82b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Stale | 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 →
audit ~92
Commits whose author or committer is not the repo's identity, and agent trailers; never rewrites. Same as `gitpro audit --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | every commit on the branch |
| path | string | yes | a directory inside the git repository (absolute, or relative to the server's directory) |
| range | string | – | a git revision range (default: the unpushed commits) |
No output schema declared.
No examples provided.
change_status ~53
Deprecated, removed in 0.5.0; nothing replaces it. Read the approval/apply/recovery status of a persistent change. Does not execute.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | the complete change plan ID |
No output schema declared.
No examples provided.
check_commit ~163
Deprecated, removed in 0.5.0; use why. Would gitpro's guard block this commit? Judges the committer (default: the repo's effective email) and author emails against the repo's identity and returns the reason and fix.
| Name | Type | Req | Description |
|---|---|---|---|
| author_email | string | – | the commit's author email (default: the committer) |
| committer_email | string | – | the committer email (default: what git would use in the repo) |
| message | string | – | the commit message, for the Co-Authored-By rules |
| path | string | yes | a directory inside the git repository (absolute, or relative to the server's directory) |
| remote | string | – | judge against this remote (name or url) instead of origin |
No output schema declared.
No examples provided.
draft_report ~140
Deprecated, removed in 0.5.0; use report. Draft a redacted gitpro bug report (versions, a redacted why, the last crash or denial) and the prefilled GitHub issue URL. It never sends or opens anything. Show the user the draft and the URL and let them decide; for a security problem, give them security_url instead of an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | what to report (default: bug) |
| message | string | – | what happened (redacted before it is used) |
| path | string | – | a directory inside the git repository (absolute, or relative to the server's directory) |
No output schema declared.
No examples provided.
env ~77
Shell lines that set GH_TOKEN etc. for the repo's identity: the commands that fetch the tokens, never their values. Same as `gitpro env --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | a directory inside the git repository (absolute, or relative to the server's directory) |
| shell | string | – | shell syntax (default: sh) |
No output schema declared.
No examples provided.
env_for ~92
Deprecated, removed in 0.5.0; use env. Shell lines that set GH_TOKEN etc. for the repo's identity: the commands that fetch the tokens, never their values. Same as `gitpro env --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | a directory inside the git repository (absolute, or relative to the server's directory) |
| shell | string | – | shell syntax (default: sh) |
No output schema declared.
No examples provided.
identities ~47
Deprecated, removed in 0.5.0; use setup. The configured identities (name, email, host, owners, forge accounts, signing); no key contents, no extra git settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lost ~82
Deprecated, removed in 0.5.0; use scan. Unpushed branches, stashes, dirty trees, repos without a remote and duplicate clones under the roots (offline checks only). Same as `gitpro lost --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| only | array | – | only these kinds |
| roots | array | – | directories to search (default: the configured roots) |
No output schema declared.
No examples provided.
operation_status ~53
Deprecated, removed in 0.5.0; nothing replaces it. Read the durable result of an idempotency key. Never executes or retries.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | the original operation key |
No output schema declared.
No examples provided.
preflight ~71
Deprecated, removed in 0.5.0; nothing replaces it. Versioned operation decision and state token for commit, push or GitHub PR creation. Read-only; online=true explicitly permits account/destination reads. Ready is not authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| online | boolean | – | – |
| request | object | yes | – |
No output schema declared.
No examples provided.
propose_change ~75
Deprecated, removed in 0.5.0; nothing replaces it. Read-only exact configuration/repair proposal. Does not record approval or change target files. Reports coverage by the operator's startup policy; otherwise ask a human to review its JSON with gitpro change approve --write in their terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | – |
No output schema declared.
No examples provided.
reconcile_operation ~78
Deprecated, removed in 0.5.0; nothing replaces it. Read-only inspection of recorded commit/push/PR intent versus current state. Remote reads require online=true. Does not retry writes, change the ledger outcome or prove attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | the original operation key |
| online | boolean | – | – |
No output schema declared.
No examples provided.
report ~125
Draft a redacted gitpro bug report (versions, a redacted why, the last crash or denial) and the prefilled GitHub issue URL. It never sends or opens anything. Show the user the draft and the URL and let them decide; for a security problem, give them security_url instead of an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | what to report (default: bug) |
| message | string | – | what happened (redacted before it is used) |
| path | string | – | a directory inside the git repository (absolute, or relative to the server's directory) |
No output schema declared.
No examples provided.
scan ~120
List repositories under the given roots (or only the given repos) and the identity git uses in each; never fixes anything. Same as `gitpro scan --json`; lost=true adds the `lost` member (unpushed branches, stashes, dirty trees and so on, as `gitpro scan --lost`).
| Name | Type | Req | Description |
|---|---|---|---|
| lost | boolean | – | also report work that exists only here (--lost) |
| repos | array | – | only these repositories, not the repos under them |
| roots | array | – | directories to search (default: the configured roots) |
No output schema declared.
No examples provided.
setup ~66
What `gitpro setup` would do, without doing it (`setup -n --json`): the identities, what is already set up and what is pending. ok=false means something is pending, not an error. Never changes anything; show the user `gitpro setup` to run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
which_identity ~83
Deprecated, removed in 0.5.0; use why. The git identity settings (user.name, user.email, signing, core.sshCommand) a repo uses right now and where each comes from; same as `gitpro which --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | a directory inside the git repository (absolute, or relative to the server's directory) |
No output schema declared.
No examples provided.
why ~182
Which gitpro identity a repo should use, which it really uses, why, and the fix command for every problem; same as `gitpro why --json`. Also gives the repo's git settings (`settings`) and answers "would the guard block this commit?" (`commit`; pass committer_email, author_email and message to judge a particular commit).
| Name | Type | Req | Description |
|---|---|---|---|
| author_email | string | – | the commit's author email (default: the committer) |
| committer_email | string | – | the committer email (default: what git would use in the repo) |
| message | string | – | the commit message, for the Co-Authored-By rules |
| path | string | yes | a directory inside the git repository (absolute, or relative to the server's directory) |
| remote | string | – | judge against this remote (name or url) instead of origin |
No output schema declared.
No examples provided.
How do I install the gitpro MCP server?
gitpro runs locally as a PyPI package, launched with uvx gitpro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · gitpro
claude mcp add yantrakar-gitpro -- uvx gitpro
What is the gitpro MCP server?
gitpro is an MCP server listed in the public MCP registry as io.github.Yantrakar/gitpro. Read-only checks of which git name, email and SSH key a repository uses, and why. This page covers its PyPI package (gitpro).
Is the gitpro MCP server safe to use?
gitpro scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 gitpro MCP server expose?
gitpro exposes 17 tools: which_identity, why, check_commit, scan, env_for, and 12 more. Their descriptions and schemas cost roughly 1,599 tokens of context every time the server is loaded.
Is the gitpro MCP server still maintained?
gitpro is still listed as active in the MCP registry. We last reached this channel on 17 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 gitpro MCP server under?
gitpro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.