Shiritori Dictionary (Japanese)
REMOTE · SHIRITORI.OMIKUJI.DEV
Play Japanese shiritori with a 90,000-word dictionary: check moves, suggest next words.
Available components
Last scanned (9 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 489 tokens (~163/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +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.
- 16 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 71
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 23 Oct 2026 · Probed https://shiritori.omikuji.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=omikuji.dev | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 14f2de63cee5ac82137eb86a39849ed1 |
| SANs: omikuji.dev, *.omikuji.dev | ||||||
| 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 shiritori.omikuji.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| omikuji.dev. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shiritori.omikuji.dev/mcp | Verified | 200 | |
| http (plaintext) | http://shiritori.omikuji.dev/mcp | HTTPS enforced | 301 | https://shiritori.omikuji.dev/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 →
check_move Check a shiritori move ~135
Check whether the next word correctly follows the previous word in shiritori: it must start with the previous word's last kana, it loses if it ends in ん or was already used. Also tells whether each word is in the dictionary and what the next word must start with.
| Name | Type | Req | Description |
|---|---|---|---|
| loose_dakuten | boolean | – | House rule: allow ば→は/ぱ style dakuten variants. |
| next | string | yes | The word just said. |
| previous | string | yes | The previous word (kana is safest; kanji is looked up in the dictionary). |
| used | array | – | Words already used in this game. |
No output schema declared.
No examples provided.
check_word Check a word ~62
Look up a word: is it in the dictionary, its reading, its first and last kana under shiritori rules (ー and small kana handled), whether it ends in ん, and which kana the next word must start with.
| Name | Type | Req | Description |
|---|---|---|---|
| word | string | yes | – |
No output schema declared.
No examples provided.
suggest_next Suggest next words ~178
Pick random words that can follow the previous word (or start with a given kana), excluding words already used and, by default, words ending in ん. pool "everyday" (default) uses hand-picked everyday words, "common" adds common dictionary words, "all" uses the whole dictionary.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | The previous word. |
| allow_n | boolean | – | Include words ending in ん (they lose). |
| count | integer | – | – |
| exclude | array | – | Words already used in this game. |
| genre | string | – | Theme for 食べ物しりとり etc. (everyday words only). |
| loose_dakuten | boolean | – | – |
| pool | string | – | – |
| start_char | string | – | Or: one kana to start with, e.g. "り". |
No output schema declared.
No examples provided.
How do I install the Shiritori Dictionary (Japanese) MCP server?
Shiritori Dictionary (Japanese) is a hosted endpoint at https://shiritori.omikuji.dev/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 · shiritori.omikuji.dev
claude mcp add --transport http dev-omikuji-shiritori 'https://shiritori.omikuji.dev/mcp'
What is the Shiritori Dictionary (Japanese) MCP server?
Shiritori Dictionary (Japanese) is an MCP server listed in the public MCP registry as dev.omikuji/shiritori. Play Japanese shiritori with a 90,000-word dictionary: check moves, suggest next words. This page covers its hosted endpoint (https://shiritori.omikuji.dev/mcp).
Is the Shiritori Dictionary (Japanese) MCP server safe to use?
Shiritori Dictionary (Japanese) scores 75 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 Shiritori Dictionary (Japanese) MCP server expose?
Shiritori Dictionary (Japanese) exposes 3 tools: check_move, suggest_next, check_word. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.
Does the Shiritori Dictionary (Japanese) MCP server require authentication?
No. We connected to Shiritori Dictionary (Japanese) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Shiritori Dictionary (Japanese) MCP server still maintained?
Shiritori Dictionary (Japanese) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.