# gitpro (pypi · gitpro)

Read-only checks of which git name, email and SSH key a repository uses, and why.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `gitpro`: 81/100 (this document), [markdown](https://verifymcp.io/servers/yantrakar-gitpro/gitpro.md), [page](https://verifymcp.io/servers/yantrakar-gitpro/gitpro)

## Channel facts

- Registry: `pypi`
- Package: `gitpro`
- Version: `0.4.0`
- 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-17.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 5 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Yantrakar/gitpro).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1670 tokens (~98/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 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.

## Install

### 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.

### Claude

```bash
claude mcp add yantrakar-gitpro -- uvx gitpro
```

### Cursor

```json
{
  "mcpServers": {
    "yantrakar-gitpro": {
      "command": "uvx",
      "args": [
        "gitpro"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "yantrakar-gitpro": {
      "command": "uvx",
      "args": [
        "gitpro"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add yantrakar-gitpro -- uvx gitpro
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yantrakar-gitpro": {
      "type": "local",
      "command": [
        "uvx",
        "gitpro"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yantrakar-gitpro --command uvx --arg gitpro
```

### Hermes

```yaml
mcp_servers:
  yantrakar-gitpro:
    command: "uvx"
    args: ["gitpro"]
```

### Netclaw

```json
{
  "McpServers": {
    "yantrakar-gitpro": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "gitpro"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add yantrakar-gitpro -t stdio -c uvx -a gitpro
```

### Other

```json
{
  "mcpServers": {
    "yantrakar-gitpro": {
      "command": "uvx",
      "args": [
        "gitpro"
      ]
    }
  }
}
```

## 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-17 (score 81, +16)

- [security regression] Tool safety: pass → unverified
- [security improvement] 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.
- [functional regression] Schema quality: 78 → 98
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.3.4 → 0.4.0

### 2026-10-16 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-15 (score 80)

First indexed and scored.

## MCP tools (17)

### `which_identity` (~83 tokens)

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`.

Input parameters:

- `path` (string, required): a directory inside the git repository (absolute, or relative to the server's directory)

### `why` (~182 tokens)

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).

Input parameters:

- `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, required): 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

### `check_commit` (~163 tokens)

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.

Input parameters:

- `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, required): 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

### `scan` (~120 tokens)

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`).

Input parameters:

- `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)

### `env_for` (~92 tokens)

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`.

Input parameters:

- `path` (string, required): a directory inside the git repository (absolute, or relative to the server's directory)
- `shell` (string): shell syntax (default: sh)

### `env` (~77 tokens)

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`.

Input parameters:

- `path` (string, required): a directory inside the git repository (absolute, or relative to the server's directory)
- `shell` (string): shell syntax (default: sh)

### `setup` (~66 tokens)

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.

### `lost` (~82 tokens)

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`.

Input parameters:

- `only` (array): only these kinds
- `roots` (array): directories to search (default: the configured roots)

### `audit` (~92 tokens)

Commits whose author or committer is not the repo's identity, and agent trailers; never rewrites. Same as `gitpro audit --json`.

Input parameters:

- `all` (boolean): every commit on the branch
- `path` (string, required): a directory inside the git repository (absolute, or relative to the server's directory)
- `range` (string): a git revision range (default: the unpushed commits)

### `identities` (~47 tokens)

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.

### `report` (~125 tokens)

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.

Input parameters:

- `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)

### `draft_report` (~140 tokens)

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.

Input parameters:

- `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)

### `preflight` (~71 tokens)

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.

Input parameters:

- `online` (boolean)
- `request` (object, required)

### `operation_status` (~53 tokens)

Deprecated, removed in 0.5.0; nothing replaces it. Read the durable result of an idempotency key. Never executes or retries.

Input parameters:

- `idempotency_key` (string, required): the original operation key

### `reconcile_operation` (~78 tokens)

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.

Input parameters:

- `idempotency_key` (string, required): the original operation key
- `online` (boolean)

### `propose_change` (~75 tokens)

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.

Input parameters:

- `request` (object, required)

### `change_status` (~53 tokens)

Deprecated, removed in 0.5.0; nothing replaces it. Read the approval/apply/recovery status of a persistent change. Does not execute.

Input parameters:

- `plan_id` (string, required): the complete change plan ID

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/yantrakar-gitpro/gitpro#diagnostics

## Score history

- 2026-10-17: 81
- 2026-10-16: 65
- 2026-10-15: 80

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/gitpro/
- Socket report: https://socket.dev/pypi/package/gitpro
- Repository: https://github.com/Yantrakar/gitpro
- Website: https://gitpro.dev/
- Changelog RSS feed: https://verifymcp.io/servers/yantrakar-gitpro/gitpro.xml
- Changelog JSON feed: https://verifymcp.io/servers/yantrakar-gitpro/gitpro.json
- HTML version of this page: https://verifymcp.io/servers/yantrakar-gitpro/gitpro