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.

isitdone

NPM · @AIVOLUTION/ISITDONE · SCANNED SEP 20

Make a coding agent prove it: run the repo's real tests, typecheck and lint before it says done.

81 Trust /100
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 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 0 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

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

# add to Claude Code
claude mcp add raimondasl-isitdone -- npx -y @aivolution/isitdone
// .cursor/mcp.json
{
  "mcpServers": {
    "raimondasl-isitdone": {
      "command": "npx",
      "args": [
        "-y",
        "@aivolution/isitdone"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "raimondasl-isitdone": {
      "command": "npx",
      "args": [
        "-y",
        "@aivolution/isitdone"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add raimondasl-isitdone -- npx -y @aivolution/isitdone
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "raimondasl-isitdone": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@aivolution/isitdone"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add raimondasl-isitdone --command npx --arg -y --arg @aivolution/isitdone
# ~/.hermes/config.yaml
mcp_servers:
  raimondasl-isitdone:
    command: "npx"
    args: ["-y", "@aivolution/isitdone"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "raimondasl-isitdone": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@aivolution/isitdone"
      ]
    }
  }
}
# add to Vellum
assistant mcp add raimondasl-isitdone -t stdio -c npx -a -y @aivolution/isitdone
// mcp.json
{
  "mcpServers": {
    "raimondasl-isitdone": {
      "command": "npx",
      "args": [
        "-y",
        "@aivolution/isitdone"
      ]
    }
  }
}
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.

  • 20 Sept 26 81

    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 20 Sept 2026 · Analysed npm/@aivolution/isitdone@0.5.2

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.5.2
Rekor log index 2899649083
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:d35d5f372f61f6a6e3fe76e7ac2a1033bc3cae6487e7abb0f9fd19c8b1480721f11ce6f1d223f30befd5116a77111150b27afc63afa8f75c68e82ad28

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~435 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
isitdone_detect ~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.

NameTypeReqDescription
cwdstringAbsolute 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.
NameTypeReqDescription
checksarrayyes
configSourcestring|nullyes
notesarrayyes
rootstringyes
stacksarrayyes

No examples provided.

isitdone_receipt ~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.

NameTypeReqDescription
cwdstringAbsolute 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.
NameTypeReqDescription
donebooleanyesTrue only for a PASS receipt of a full run on exactly this tree.
reasonstringyes
receiptobject|nullyes
rootstring
statestringyes
treestringHash of the current working tree.

No examples provided.

isitdone_verify ~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.

NameTypeReqDescription
basestringGit ref to diff against for the test-integrity scan. Default: HEAD, i.e. the uncommitted changes.
claimstringThe completion claim you are about to make, quoted; it is recorded in the receipt.
cwdstringAbsolute 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.
profilestringfull (default) runs every check. lite runs only typecheck and lint and never reports done: true.
strictbooleanAlso answer NOT DONE when the change weakened tests (high or critical findings), even if the checks pass.
NameTypeReqDescription
cachedbooleanyesA PASS receipt already proved this exact tree; nothing was re-run.
checksarrayyes
claimstring|null
donebooleanyesTrue only when every full check passed on exactly this working tree and no test-integrity finding blocks.
durationMsnumber
gitobject
integrityobject|nullyesScan of the change set for weakened tests (deleted tests, new skips, dropped or downgraded assertions, neutered configuration).
noChecksbooleanyesNo checks were detected, so nothing was verified.
notesarray
okbooleanyesEvery check that ran passed. With profile lite this can be true while done is false.
profilestringyes
receiptobject|nullyes
skippedarrayyes
stacksarray
statestringyesThe receipt this run wrote or reused.
versionstring
warningsarray

No examples provided.

Common questions

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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.