# io.github.Yuikij/mcp-turtle-noir (remote · turtlenoir.com)

Play Turtle Soup (lateral thinking puzzles) against a strict AI host with yes/no questioning.

- Trust score: 65/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `turtlenoir.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/yuikij-mcp-turtle-noir/turtlenoir.md), [page](https://verifymcp.io/servers/yuikij-mcp-turtle-noir/turtlenoir)
- npm · `mcp-turtle-noir`: 59/100, [markdown](https://verifymcp.io/servers/yuikij-mcp-turtle-noir/mcp-turtle-noir.md), [page](https://verifymcp.io/servers/yuikij-mcp-turtle-noir/mcp-turtle-noir)

## Channel facts

- Endpoint: `https://turtlenoir.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 347 tokens (~115/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yuikij-mcp-turtle-noir https://turtlenoir.com/mcp
```

### Codex

```toml
[mcp_servers.yuikij-mcp-turtle-noir]
url = "https://turtlenoir.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yuikij-mcp-turtle-noir": {
      "type": "remote",
      "url": "https://turtlenoir.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yuikij-mcp-turtle-noir --url https://turtlenoir.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yuikij-mcp-turtle-noir:
    url: "https://turtlenoir.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (3)

### `start_session` (~120 tokens)

Start a Turtle Soup puzzle session

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.

Input parameters:

- `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.

### `ask_question` (~93 tokens)

Ask the AI host a question

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).

Input parameters:

- `question` (string, required): The question to ask (max 300 chars).
- `session_id` (string, required): Session id returned by start_session.

### `give_up_and_reveal` (~43 tokens)

Give up and reveal the solution

Reveal the hidden solution and end the session. Only allowed once solve progress reaches 60.

Input parameters:

- `session_id` (string, required): Session id returned by start_session.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yuikij-mcp-turtle-noir/turtlenoir#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://turtlenoir.com/mcp
- Repository: https://github.com/Yuikij/mcp-turtle-noir
- Website: https://turtlenoir.com/
- Changelog RSS feed: https://verifymcp.io/servers/yuikij-mcp-turtle-noir/turtlenoir/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yuikij-mcp-turtle-noir/turtlenoir/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yuikij-mcp-turtle-noir/turtlenoir