io.github.Yuikij/mcp-turtle-noir
REMOTE · TURTLENOIR.COM · 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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 347 tokens (~115/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 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
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; 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 is a hosted endpoint at https://turtlenoir.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · turtlenoir.com
claude mcp add --transport http yuikij-mcp-turtle-noir 'https://turtlenoir.com/mcp'
{
"mcpServers": {
"yuikij-mcp-turtle-noir": {
"url": "https://turtlenoir.com/mcp"
}
}
} {
"servers": {
"yuikij-mcp-turtle-noir": {
"type": "http",
"url": "https://turtlenoir.com/mcp"
}
}
} [mcp_servers.yuikij-mcp-turtle-noir] url = "https://turtlenoir.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yuikij-mcp-turtle-noir": {
"type": "remote",
"url": "https://turtlenoir.com/mcp",
"enabled": true
}
}
} openclaw mcp add yuikij-mcp-turtle-noir --url 'https://turtlenoir.com/mcp' --transport streamable-http
mcp_servers:
yuikij-mcp-turtle-noir:
url: "https://turtlenoir.com/mcp" {
"McpServers": {
"yuikij-mcp-turtle-noir": {
"Transport": "http",
"Url": "https://turtlenoir.com/mcp"
}
}
} assistant mcp add yuikij-mcp-turtle-noir -t streamable-http -u 'https://turtlenoir.com/mcp'
{
"mcpServers": {
"yuikij-mcp-turtle-noir": {
"type": "http",
"url": "https://turtlenoir.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 · Probed https://turtlenoir.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=turtlenoir.com | CN=WE1,O=Google Trust Services,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6522d76844f06d5d0e2c4fdc568a8d34 |
| SANs: turtlenoir.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of turtlenoir.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| turtlenoir.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://turtlenoir.com/mcp | Verified | 200 | |
| http (plaintext) | http://turtlenoir.com/mcp | HTTPS enforced | 301 | https://turtlenoir.com/mcp |
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 Ask the AI host a question ~93
Ask one yes/no style question about the current puzzle. The AI host answers with one of four judgments: 是(Yes) / 不是(No) / 是也不是(Both) / 没有关系(Irrelevant), plus solve progress (0-100).
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to ask (max 300 chars). |
| session_id | string | yes | Session id returned by start_session. |
No output schema declared.
No examples provided.
give_up_and_reveal Give up and reveal the solution ~43
Reveal the hidden solution and end the session. Only allowed once solve progress reaches 60.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Session id returned by start_session. |
No output schema declared.
No examples provided.
start_session Start a Turtle Soup puzzle session ~120
Start a new Turtle Soup (lateral thinking puzzle) session. Returns the surface story; the hidden solution stays on the server. Optional filters: region (CN/US/JP), difficulty, keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | string | – | Preferred difficulty: 'easy' or 'hard'. Defaults to both. |
| keyword | string | – | Optional keyword to match in puzzle title/surface/tags. |
| region | string | – | Puzzle region: 'CN' (Chinese), 'US' (English), or 'JP' (Japanese). Defaults by caller location. |
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 hosted endpoint (https://turtlenoir.com/mcp).
Is the io.github.Yuikij/mcp-turtle-noir server safe to use?
io.github.Yuikij/mcp-turtle-noir scores 78 out of 100 on VerifyMCP. 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 256 tokens of context every time the server is loaded.
Does the io.github.Yuikij/mcp-turtle-noir server require authentication?
No. We connected to io.github.Yuikij/mcp-turtle-noir without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.