# gitdone (pypi · gitdone)

Read-only project status: strict and weighted completion, each claim held to git.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `gitdone`: 66/100 (this document), [markdown](https://verifymcp.io/servers/artjack-gitdone/gitdone.md), [page](https://verifymcp.io/servers/artjack-gitdone/gitdone)

## Channel facts

- Registry: `pypi`
- Package: `gitdone`
- Version: `0.3.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-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - 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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ArtJack/gitdone).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 740 tokens (~74/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 gitdone MCP server?

gitdone runs locally as a PyPI package, launched with uvx gitdone. 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 artjack-gitdone -- uvx gitdone
```

### Cursor

```json
{
  "mcpServers": {
    "artjack-gitdone": {
      "command": "uvx",
      "args": [
        "gitdone"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "artjack-gitdone": {
      "command": "uvx",
      "args": [
        "gitdone"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add artjack-gitdone -- uvx gitdone
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add artjack-gitdone --command uvx --arg gitdone
```

### Hermes

```yaml
mcp_servers:
  artjack-gitdone:
    command: "uvx"
    args: ["gitdone"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add artjack-gitdone -t stdio -c uvx -a gitdone
```

### Other

```json
{
  "mcpServers": {
    "artjack-gitdone": {
      "command": "uvx",
      "args": [
        "gitdone"
      ]
    }
  }
}
```

## 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-11-05 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80)

First indexed and scored.

## MCP tools (10)

### `status` (~56 tokens)

Where the project stands: strict and weighted percent per group, the next workstream, what it needs.

Input parameters:

- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `rows` (~68 tokens)

The rows of the status table, optionally only the ones not yet at the strict kind.

Input parameters:

- `open` (boolean): Only rows not yet at the strict kind.
- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `evidence` (~75 tokens)

Every row with what it claims as evidence, and what git and gh say about each claim.

Input parameters:

- `offline` (boolean): Do not call gh or glab; a pull request stays unverified.
- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `check` (~80 tokens)

Run the gate: is the view true, do the counts sum, does each status have its evidence. Writes nothing.

Input parameters:

- `offline` (boolean): Do not call gh or glab; a pull request stays unverified.
- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `week` (~72 tokens)

What moved since a date, a span like '2 weeks', or a commit, from the table's git history. Default: 7 days.

Input parameters:

- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.
- `since` (string)

### `eta` (~95 tokens)

When it will be done if the work goes on as it has: a line through the table's git history, with a range, the scope's effect and the deadline. Experimental: give a date only when asked when it will be done, quote its words, and say it is a line.

Input parameters:

- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `focus` (~79 tokens)

Where the recent commits went: on plan, upkeep or off plan, with the reason for each. A signal, never a gate.

Input parameters:

- `days` (integer): How many days to read. Default: 14.
- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `next` (~64 tokens)

What to work on now: the next workstream's open rows. Anything else is a change of scope, so say so before starting it.

Input parameters:

- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `matrix` (~89 tokens)

A traceability matrix: each requirement, the row that holds it, its evidence and the tests on record. A test listed exists; passing is CI's word.

Input parameters:

- `offline` (boolean): Do not call gh or glab; a pull request stays unverified.
- `project` (string): A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

### `portfolio` (~39 tokens)

Every tracked project under a folder: strict, weighted, next, and the gate read offline.

Input parameters:

- `folder` (string): Default: the server's folder.

## Diagnostics

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

## Score history

- 2026-11-05: 66
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80

## Common questions

### What is the gitdone MCP server?

gitdone is an MCP server listed in the public MCP registry as io.github.ArtJack/gitdone. Read-only project status: strict and weighted completion, each claim held to git. This page covers its PyPI package (gitdone).

### Is the gitdone MCP server safe to use?

gitdone scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 gitdone MCP server expose?

gitdone exposes 10 tools: status, rows, evidence, check, week, and 5 more. Their descriptions and schemas cost roughly 717 tokens of context every time the server is loaded.

### Is the gitdone MCP server still maintained?

gitdone is still listed as active in the MCP registry. We last reached this channel on 5 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 gitdone MCP server under?

gitdone 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/gitdone/
- Socket report: https://socket.dev/pypi/package/gitdone
- Repository: https://github.com/ArtJack/gitdone
- Changelog RSS feed: https://verifymcp.io/servers/artjack-gitdone/gitdone.xml
- Changelog JSON feed: https://verifymcp.io/servers/artjack-gitdone/gitdone.json
- HTML version of this page: https://verifymcp.io/servers/artjack-gitdone/gitdone