Remote MCP · Endpoint

Oh, my Dots! MCP server

No. Oh, my Dots! answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.ohmydots.com/mcp

The last check completed an MCP handshake.

Registry name
com.ohmydots/mcp
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
417 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Crossword, audio crossword, word search, cryptogram and cross-math puzzle links for ohmydots.com.
Listing
From the official MCP registry (active).
Recent checks of Oh, my Dots!
CheckedResultHandshake
7 hours agoHandshake completed417 ms
4 days agoHandshake completed970 ms
14 days agoHandshake completed218 ms
15 days agoHandshake completed465 ms
15 days agoHandshake completed841 ms
17 days agoHandshake completed510 ms
18 days agoHandshake completed509 ms
19 days agoHandshake completed653 ms
20 days agoHandshake completed520 ms
21 days agoHandshake completed516 ms
23 days agoHandshake completed570 ms
26 days agoHandshake completed509 ms
28 days agoHandshake completed553 ms

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

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 Oh, my Dots! and makes no claim about it beyond what these checks measured.