Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
nir414
Source: github_code
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
GPL_BRIDGEVS Code 확장 브리지 사용. auto=확장이 있으면 확장 세션으로, 없으면 직접 접속 / only=브리지 필수(세션 단일화 보장) / off=항상 직접 접속GPL_HOST제어기 IPGPL_IDLE_CLOSE_MSkeep-alive 1402 소켓의 유휴 종료 시간(ms)GPL_LOCK_WAIT_MS배포 잠금 대기 상한(ms). VS Code 확장이 FTP 업로드/배포 중이면 %TEMP%\gpl-controller\<ip>.lock.json을 잡는다. 이때 compile_project/start_project/unload_project와 controller_command의 Compile/Start/Load/Unload는 잠금이 풀릴 때까지 이 시간만 기다렸다 진행하고, 초과 시 보유자 정보와 함께 거부한다(업로드 도중 Compile/Start는 제어기 이상 유발 — GitHub #17)GPL_MCP_LOG_DIR세션 로그 파일 디렉터리(도구 호출/1402 명령 기록)GPL_PORTASCII 콘솔 포트GPL_PROJECT기본 프로젝트명(도구에서 생략 시 사용)GPL_TIMEOUT_MS명령 타임아웃(ms). compile은 최소 60s로 자동 상향GPL_VSCODE_CLI확장이 비활성일 때 깨우는 데 쓸 VS Code CLI 경로Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
25/25 tools missing one or more hints — controller_command (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_dataids (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_session_log (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Descriptions match behaviour
3 tools describe read intent but their handlers mutate — list_breakpoints (line 109: fs.appendFileSync(LOG_FILE, line + '\n')); show_thread (line 109: fs.appendFileSync(LOG_FILE, line + '\n')); show_stack (line 109: fs.appendFileSync(LOG_FILE, line + '\n'))
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tool test coverage
Only 2/25 tools referenced in tests (8%)
Write tests that reference each tool by name so every tool has at least one test.
Tool description accuracy
3 tools have description/behavior mismatches: list_breakpoints: description implies read-only but handler writes/deletes/executes; show_thread: description implies read-only but handler writes/deletes/executes; show_stack: description implies read-only but handler writes/deletes/executes
Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/nir414/gpl_language)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check