Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

gitdone

PYPI · GITDONE

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

Available components

66 Trust /100

Last scanned (3 hours ago)

Scores higher than 62% of PyPI servers

Category Project Management

Trust breakdown (7 categories)

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

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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +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.

  • 1 Nov 26 80

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed pypi/gitdone@0.3.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 ArtJack/gitdone
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ArtJack/gitdone/.github/workflows/release.yml@refs/tags/v0.3.0
Rekor log index 3628358416
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:4dd2ee3f6bf22ff32d58d7082d32c0bf81bcf2c6809a8ab5c169f33baef8b92c

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~717 tokens

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 →

Tool Tokens
check ~80

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

NameTypeReqDescription
offlineboolean–Do not call gh or glab; a pull request stays unverified.
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

eta ~95

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.

NameTypeReqDescription
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

evidence ~75

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

NameTypeReqDescription
offlineboolean–Do not call gh or glab; a pull request stays unverified.
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

focus ~79

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

NameTypeReqDescription
daysinteger–How many days to read. Default: 14.
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

matrix ~89

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.

NameTypeReqDescription
offlineboolean–Do not call gh or glab; a pull request stays unverified.
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

next ~64

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

NameTypeReqDescription
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

portfolio ~39

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

NameTypeReqDescription
folderstring–Default: the server's folder.

No output schema declared.

No examples provided.

rows ~68

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

NameTypeReqDescription
openboolean–Only rows not yet at the strict kind.
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

status ~56

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

NameTypeReqDescription
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.

No output schema declared.

No examples provided.

week ~72

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

NameTypeReqDescription
projectstring–A project folder or a plan file. Default: found from the server's folder through .gitdone.json.
sincestring––

No output schema declared.

No examples provided.

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.

pypi · gitdone

# add to Claude Code
claude mcp add artjack-gitdone -- uvx gitdone
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.