io.github.Yuikij/mcp-turtle-noir
NPM · MCP-TURTLE-NOIR · 2 COMPONENTS · SCANNED SEP 20
Play Turtle Soup (lateral thinking puzzles) against a strict AI host with yes/no questioning.
Available components
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 7 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 271 tokens (~90/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Yuikij/mcp-turtle-noir server?
io.github.Yuikij/mcp-turtle-noir runs locally as an npm package, launched with npx -y mcp-turtle-noir. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-turtle-noir
claude mcp add yuikij-mcp-turtle-noir -- npx -y mcp-turtle-noir
{
"mcpServers": {
"yuikij-mcp-turtle-noir": {
"command": "npx",
"args": [
"-y",
"mcp-turtle-noir"
]
}
}
} {
"servers": {
"yuikij-mcp-turtle-noir": {
"command": "npx",
"args": [
"-y",
"mcp-turtle-noir"
]
}
}
} codex mcp add yuikij-mcp-turtle-noir -- npx -y mcp-turtle-noir
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yuikij-mcp-turtle-noir": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-turtle-noir"
],
"enabled": true
}
}
} openclaw mcp add yuikij-mcp-turtle-noir --command npx --arg -y --arg mcp-turtle-noir
mcp_servers:
yuikij-mcp-turtle-noir:
command: "npx"
args: ["-y", "mcp-turtle-noir"] {
"McpServers": {
"yuikij-mcp-turtle-noir": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-turtle-noir"
]
}
}
} assistant mcp add yuikij-mcp-turtle-noir -t stdio -c npx -a -y mcp-turtle-noir
{
"mcpServers": {
"yuikij-mcp-turtle-noir": {
"command": "npx",
"args": [
"-y",
"mcp-turtle-noir"
]
}
}
} 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.
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/mcp-turtle-noir@1.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 7 |
| 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 →
ask_question ~83
Ask a question for the active session. Detect user language and pass language (zh-CN/en-US/ja-JP).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | User language for localized response, e.g. zh-CN/en-US/ja-JP |
| question | string | yes | Detective question to judge |
| session_id | string | yes | Session ID returned by start_session |
No output schema declared.
No examples provided.
give_up_and_reveal ~78
Give up the current session and reveal the full story. Detect user language and pass language (zh-CN/en-US/ja-JP).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | User language for localized response, e.g. zh-CN/en-US/ja-JP |
| session_id | string | yes | Session ID returned by start_session |
No output schema declared.
No examples provided.
start_session ~110
Start a new Turtle Soup session. Detect user language and pass language (zh-CN/en-US/ja-JP). Optional: region, difficulty, keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | string | – | Optional difficulty preference |
| keyword | string | – | Optional fuzzy keyword on title/surface/tags |
| language | string | – | User language for localized response, e.g. zh-CN/en-US/ja-JP |
| region | string | – | Optional region code, e.g. US/CN/JP |
No output schema declared.
No examples provided.
What is the io.github.Yuikij/mcp-turtle-noir server?
io.github.Yuikij/mcp-turtle-noir is listed in the public MCP registry as io.github.Yuikij/mcp-turtle-noir. Play Turtle Soup (lateral thinking puzzles) against a strict AI host with yes/no questioning. This page covers its npm package (mcp-turtle-noir).
Is the io.github.Yuikij/mcp-turtle-noir server safe to use?
io.github.Yuikij/mcp-turtle-noir scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.Yuikij/mcp-turtle-noir server expose?
io.github.Yuikij/mcp-turtle-noir exposes 3 tools: start_session, ask_question, give_up_and_reveal. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.
Is the io.github.Yuikij/mcp-turtle-noir server still maintained?
io.github.Yuikij/mcp-turtle-noir 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 io.github.Yuikij/mcp-turtle-noir server under?
io.github.Yuikij/mcp-turtle-noir declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.