프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요
초보자 모드 끄기
색상시스템 설정라이트다크
언어ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 메뉴설정
초보자 모드 끄기
색상시스템 설정라이트다크
언어ไทยEnglish中文日本語한국어EspañolDeutsch

isitdone

제작자: raimondasl버전 0.9.0i★ –i내 컴퓨터에서 실행
레지스트리 이름io.github.raimondasl/isitdone

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: stdio
  • 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

  • 기본 점검: 1개 중 1개 통과
  • 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
  • 레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

  • npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "isitdone": {
      "command": "npx",
      "args": [
        "-y",
        "@aivolution/isitdone",
        "mcp"
      ]
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add isitdone -- npx -y @aivolution/isitdone mcp

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "isitdone": {
      "command": "npx",
      "args": [
        "-y",
        "@aivolution/isitdone",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "isitdone": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@aivolution/isitdone",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 raimondasl 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 32688개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 32688개 중 68%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 32688개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

isitdone, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.9.0)은 18일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, 御府和田玉 在售作品查询

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211그저께 업데이트
설치

Live in-stock Hetian jade from Yufu, Shanghai: prices, monthly price guide, book a viewing.

클라우드에서 실행오늘 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

isitdone

Don't let your coding agent say "done" until the tests actually pass.

*Rendered from a real run (npm run demo): the agent lines are narration; the hook and CLI output are captured as-is, with only the temporary path shortened.*

isitdone is a zero-LLM, zero-dependency Stop hook and CLI for Claude Code, Codex CLI, Cursor, Gemini CLI, GitHub Copilot CLI, Qwen Code, Goose, Factory Droid, Devin, Augment, OpenCode and Junie CLI. When the agent tries to end its turn claiming the work is complete, isitdone runs the repository's *real* test, typecheck and lint commands on the *exact* working tree, scans the diff for weakened tests, and refuses the stop until they pass. It also tells the agent mid-turn when an edit just weakened a test, runs the same verification on pull requests as a GitHub Action, offers it as an MCP server to agents that have no stop hook, and leaves a git-bound receipt you can paste into a PR.

npx isitdone init

No API keys. No network. No telemetry. Just exit codes.

The moment it exists for

Claude Code ends its turn with:

Done. All 4 tests pass and the auth refactor is complete.

The Stop hook runs isitdone before that turn is allowed to end. The agent receives this instead:

isitdone: NOT DONE. 1 check failed on the current working tree (attempt 1/3).

You claimed: "All 4 tests pass and the auth refactor is complete."

npm run typecheck PASS npm run lint PASS npm test FAIL 1 failed, 3 passed

--- npm test (last 24 lines) --- ✖ failing tests:

test at test/auth.test.js:14:1 ✖ is case-insensitive about the scheme (1.498ms) AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

null !== 'abc' ...

Fix the failures, then run npx isitdone and paste its output before claiming completion. Do not skip, delete or weaken tests to make this pass; if a check is wrong for this repo, say so explicitly to the user.

The agent keeps working. When it genuinely finishes:

$ npx isitdone

isitdone main@2429c82 dirty (1 file)

npm run typecheck PASS 428ms npm run lint PASS 411ms npm test PASS 532ms

DONE receipt -> PASS (tree e5e47d9, 3 checks, 1.8s)

$ npx isitdone receipt --md # paste into the PR

checkresulttime
npm run typecheckPASS428ms
npm run lintPASS411ms
npm testPASS532ms

Tree e5e47d9 on main@2429c82 (+1 uncommitted). Receipt: PASS · isitdone 0.1.0

Edit one more file and the receipt goes STALE until the checks run again. A hand-edited receipt reads NONE. (isitdone on npm is a short alias of @aivolution/isitdone; both commands are the same program.)

How often does this actually happen?

Measure it on your own machine. isitdone history reads the transcripts already on disk: Claude Code (~/.claude/projects), Codex CLI (~/.codex/sessions: legacy, paginated and pre-0.40 rollouts, honouring /undo rollbacks), Gemini CLI (~/.gemini/tmp/ /chats, both the .json and the 0.39+ .jsonl layouts), Qwen Code (~/.qwen/projects/ /chats) and Cursor (the IDE's state.vscdb bubble store, opened read-only in place, which needs Node 22.13+ or 24 for node:sqlite; on Node 20 the agent-transcripts JSONL is read instead, which carries no exit codes, and the report says so). It finds every turn where the agent edited files and then claimed completion, and checks whether a test command actually passed after the last edit. Nothing leaves your machine; only counts are printed.

$ npx isitdone history --until 2026-09-07 --exclude <private project>

isitdone history ~/.claude/projects until 2026-09-07 scanned 596 sessions in 6 projects; 1320 turns edited files; 495 of those ended with a completion claim; 1 project dir excluded claude-code 596 sessions 495 claims 35% verified

VERIFIED 35% (173) a test command passed after the last edit STALE 35% (174) tests passed, then more edits, no re-run FAILED 1% (3) the last test run failed, "done" claimed anyway NEVER RAN 29% (145) no test command in the turn at all

65% of "done" claims (322 of 495) had no passing test run behind them. 21 of the verified claims had a failed test run earlier in the same turn; only the last command passed, and it may have been a narrower one (--verbose marks them).

That is the author's real result, printed by isitdone 0.8.2 on 2026-09-27 over the Claude Code sessions that were on disk before the gate went in: claims dated 2026-06-20 to 2026-09-07, which --until 2026-09-07 reproduces. One private project is left out with --exclude, as it was in every published run; the only other edits are the home directory shortened to ~ and the per-project lines at the end dropped. The first published figure came from isitdone 0.2.0 on 2026-09-07: 69% of 516 claims (31% verified, 37% stale, 31% never ran, and a failing-run row printed as 0%; under 0.2.0's plain rounding that means at most 2 claims). Later versions detect claims and turns more strictly, over the same transcripts. Since 0.8.1 history prints the count beside every share (since 0.8.2 the headline too) and never rounds a row that holds anything to 0%, so a 0% row now means none. Post yours.

Once the gate is installed, that measure alone undercounts: the verification happens inside the Stop hook, and a transcript does not show the hook's run as a test the agent ran. So the hook keeps a local log of its own decisions (.isitdone/decisions.jsonl: one line per stop with the outcome, whether the final message claimed completion, and check counts; no message text, no paths, the session id only hashed), and history adds what the gate did in the projects it scanned. The layout, with illustrative numbers:

  gate  the isitdone Stop hook decided 132 stops in 2 projects (.isitdone/decisions.jsonl)

97 passed; 21 turns blocked: 18 fixed and then passed, 2 gave up after the cap, 1 released 64 stops claimed done; 12 of them were refused (19%)

 The longer story of why the gate sits where it does is in [docs/why.md](docs/why.md) (also [on DEV](https://dev.to/raimondasl/69-of-my-coding-agents-done-claims-werent-here-is-the-gate-i-put-in-front-of-them-lho), where comments are open).

Install

One command per host. Run it inside the repository.

HostCommandWhere it writes
Claude Codenpx isitdone init.claude/settings.json (Stop)
Codex CLInpx isitdone init --agent codex.codex/hooks.json (Stop), then run /hooks in Codex and trust it
Cursornpx isitdone init --agent cursor.cursor/hooks.json (stop)
Gemini CLInpx isitdone init --agent gemini.gemini/settings.json (AfterAgent); or gemini extensions install https://github.com/raimondasl/isitdone-gemini
GitHub Copilot CLInpx isitdone init --agent copilot.github/hooks/isitdone.json (agentStop); restart Copilot
Qwen Codenpx isitdone init --agent qwen.qwen/settings.json (Stop)
Goosenpx isitdone init --agent goose.agents/plugins/isitdone/hooks/hooks.json (Stop)
Factory Droidnpx isitdone init --agent droid.factory/hooks.json (Stop)
Devinnpx isitdone init --agent devin.devin/hooks.v1.json (Stop); skipped when the Claude Code hook is present, since Devin loads that too
Augment (Auggie)npx isitdone init --agent augment.augment/settings.json (Stop) pointing at .augment/hooks/isitdone-hook.sh/.cmd, since Auggie runs script files
OpenCodenpx isitdone init --agent opencode.opencode/plugins/isitdone.js (a plugin: OpenCode has no blocking hook, so failed checks come back as a visible [isitdone] follow-up message in the same session)
Junie CLI (early access)npx isitdone init --agent junie --user~/.junie/config.json (Stop)
Everythingnpx isitdone init --agent allall of the above that apply to the repo

init detects the checks, writes the Stop hook and (for Claude Code, Codex, Gemini CLI, Qwen Code, Devin and OpenCode) a warn-only post-edit hook, adds .isitdone/ to .gitignore, and runs doctor, which pipes a synthetic "all tests pass" stop event through the hook and proves it blocks, and runs the detected checks once on the current tree so that a wrong guess (say mypy . where CI runs mypy src/pkg) or an already-red tree shows up now, at install time, instead of as NOT DONE on every stop:

$ npx isitdone init

isitdone init ~/work/demo-app detected npm run typecheck, npm run lint, npm test profile claim-gated (lite checks on every stop, full checks when the agent claims done) gitignore added .isitdone/ Claude Code added .claude/settings.json

isitdone doctor ~/work/demo-app ok git main@2429c82, 0 dirty file(s), tree 8d11d2f ok config no .isitdone.json (auto-detect only) ok checks typecheck: npm run typecheck [lite, 60s]; lint: npm run lint [lite, 60s]; test: npm test [full, 120s] ok baseline all 3 checks pass on the current tree (npm run typecheck 428ms, npm run lint 411ms, npm test 532ms) ok hook:claude Claude Code (project) .claude/settings.json -> npx -y @aivolution/isitdone hook --host claude ok probe:claude synthetic "tests pass" stop was blocked in 1.9s (decision block with reason)

OK the agent cannot claim done with failing checks in this repo

Claude Code users can also install it as a plugin: /plugin marketplace add raimondasl/isitdone then /plugin install isitdone@isitdone. Gemini CLI users can install it as an extension: gemini extensions install https://github.com/raimondasl/isitdone-gemini (isitdone-gemini). A paste-to-agent version of these instructions is in docs/install.md. How each of these agents' end-of-turn hooks works (config file, payload, how to block, loop flags) is written up vendor-neutrally in docs/agent-hooks.md, with the same table as data in docs/agent-hooks.json.

Add --user to install into your user-level settings instead of the project. npx isitdone uninstall removes it. Teach the agent to run it itself with npx skills add raimondasl/isitdone (the SKILL.md is at the repo root).

The code lives in the @aivolution/isitdone package; isitdone on npm is a short alias with the same command, and installed hooks always call the canonical package. npm i -D @aivolution/isitdone makes the hook resolve locally, with no registry lookup and offline.

Updating

The hook runs through npx, which keeps its own install cache and does not refresh an unpinned package by itself. To move the hook to the latest release:

npx isitdone update          # clears the cached copies of both packages and re-warms them

npx isitdone update --check # only reports whether a newer release exists

doctor reports the version the hook actually runs and mentions when a newer release is available. Projects that installed @aivolution/isitdone as a dev dependency update it with npm update @aivolution/isitdone instead.

Mid-turn warnings

The Stop hook is the gate; the post-edit hook is the nudge. On Claude Code, Codex, Gemini CLI, Qwen Code, Devin and OpenCode, init also registers a hook that runs after every Edit/Write (Codex and Devin: apply_patch, Gemini and Qwen: write_file/replace, OpenCode: edit/write/apply_patch). It scans just that file against HEAD (so it sees every uncommitted change to the file, not only the lines this edit touched) and, when the tests got weaker, ad

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기