isitdone
NPM · @AIVOLUTION/ISITDONE
Make a coding agent prove it: run the repo's real tests, typecheck and lint before it says done.
Available components
Last scanned (20 hours ago)
Scores higher than 98% of npm servers
Category Testing and QA
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to raimondasl/isitdone). 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 594 tokens (~198/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Package version: 0.8.2 → 0.9.0 functional
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 npm/@aivolution/isitdone@0.9.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | raimondasl/isitdone |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/raimondasl/isitdone/.github/workflows/release.yml@refs/tags/v0.9.0 |
| Rekor log index | 3338777419 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c1fa534d77cad11cd2e9ea490198afdb46719b082ecca8e22e39a6acbf5de04e19f52cf154ee76c4eec0913006b17a2030b478544f2525014ba4aa479 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
isitdone_detect isitdone: which checks would run ~80
Read-only, runs nothing. The check commands isitdone_verify would run in this repository: id, command, lite or full, timeout, and where each one was detected.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Absolute path of the repository, or of a directory inside it. Default: the client's first workspace root, else the directory the server was started in. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| configSource | string|null | yes | – |
| notes | array | yes | – |
| root | string | yes | – |
| stacks | array | yes | – |
No examples provided.
isitdone_receipt isitdone: receipt for the current tree ~89
Read-only, runs nothing. Whether the current working tree already has a verification receipt: PASS (the checks passed on exactly this tree), FAIL, STALE (files or the check configuration changed since) or NONE.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Absolute path of the repository, or of a directory inside it. Default: the client's first workspace root, else the directory the server was started in. |
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | yes | True only for a PASS receipt of a full run on exactly this tree. |
| reason | string | yes | – |
| receipt | object|null | yes | – |
| root | string | – | – |
| state | string | yes | – |
| tree | string | – | Hash of the current working tree. |
No examples provided.
isitdone_verify isitdone: verify before claiming done ~266
Run this repository's real test, typecheck and lint commands on the current working tree, scan the diff for weakened tests, and write a receipt bound to that exact tree. Call it before you tell the user that work is complete, fixed, passing or ready for review, and paste the result. NOT DONE (done: false) is an answer, not a tool failure: fix the code and call again. Never skip, delete or weaken tests to make it pass. A PASS receipt for an unchanged tree is reused, so calling again is cheap.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Git ref to diff against for the test-integrity scan. Default: HEAD, i.e. the uncommitted changes. |
| claim | string | – | The completion claim you are about to make, quoted; it is recorded in the receipt. |
| cwd | string | – | Absolute path of the repository, or of a directory inside it. Default: the client's first workspace root, else the directory the server was started in. |
| profile | string | – | full (default) runs every check. lite runs only typecheck and lint and never reports done: true. |
| strict | boolean | – | Also answer NOT DONE when the change weakened tests (high or critical findings), even if the checks pass. |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | yes | A PASS receipt already proved this exact tree; nothing was re-run. |
| checks | array | yes | – |
| claim | string|null | – | – |
| done | boolean | yes | True only when every full check passed on exactly this working tree and no test-integrity finding blocks. |
| durationMs | number | – | – |
| git | object | – | – |
| integrity | object|null | yes | Scan of the change set for weakened tests (deleted tests, new skips, dropped or downgraded assertions, neutered configuration). |
| noChecks | boolean | yes | No checks were detected, so nothing was verified. |
| notes | array | – | – |
| ok | boolean | yes | Every check that ran passed. With profile lite this can be true while done is false. |
| profile | string | yes | – |
| receipt | object|null | yes | – |
| skipped | array | yes | – |
| stacks | array | – | – |
| state | string | yes | The receipt this run wrote or reused. |
| version | string | – | – |
| warnings | array | – | – |
No examples provided.
How do I install the isitdone MCP server?
isitdone runs locally as an npm package, launched with npx -y @aivolution/isitdone. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @aivolution/isitdone
claude mcp add raimondasl-isitdone -- npx -y @aivolution/isitdone
What is the isitdone MCP server?
isitdone is an MCP server listed in the public MCP registry as io.github.raimondasl/isitdone. Make a coding agent prove it: run the repo's real tests, typecheck and lint before it says done. This page covers its npm package (@aivolution/isitdone).
Is the isitdone MCP server safe to use?
isitdone scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 isitdone MCP server expose?
isitdone exposes 3 tools: isitdone_verify, isitdone_receipt, isitdone_detect. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.
Is the isitdone MCP server still maintained?
isitdone 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 isitdone MCP server under?
isitdone declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.