Remote MCP · Endpoint

Shiritori Dictionary (Japanese) MCP server

No. Shiritori Dictionary (Japanese) answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://shiritori.omikuji.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.omikuji/shiritori
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
471 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Play Japanese shiritori with a 90,000-word dictionary: check moves, suggest next words.
Listing
From the official MCP registry (active).
Recent checks of Shiritori Dictionary (Japanese)
CheckedResultHandshake
43 minutes agoHandshake completed471 ms
8 days agoHandshake completed318 ms
9 days agoHandshake completed236 ms
11 days agoHandshake completed203 ms
12 days agoHandshake completed378 ms
13 days agoHandshake completed664 ms
14 days agoHandshake completed241 ms
14 days agoHandshake completed304 ms
16 days agoHandshake completed455 ms
19 days agoHandshake completed239 ms
21 days agoHandshake completed257 ms
24 days agoHandshake completed212 ms
26 days agoHandshake completed224 ms
28 days agoHandshake completed184 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Shiritori Dictionary (Japanese) and makes no claim about it beyond what these checks measured.