Remote MCP · Endpoint
DomChecker MCP server
No. DomChecker answered an MCP handshake 37 minutes ago.
UpLast checked 37 minutes ago
Server URL
https://domchecker.ru/mcp
The last check completed an MCP handshake.
- Registry name
- ru.domchecker/domain-checker
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 414 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 83.3% from 12 checks
- Described by its publisher as
- Domain availability, WHOIS and DNS for any TLD (.ru, .рф, .com…), straight from registries.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 37 minutes ago | Handshake completed | 414 ms |
| 4 days ago | Handshake completed | 487 ms |
| 7 days ago | Handshake completed | 442 ms |
| 16 days ago | Handshake completed | 1.43 s |
| 16 days ago | Handshake completed | 407 ms |
| 18 days ago | Handshake completed | 959 ms |
| 19 days ago | Failed - the hostname does not resolve | — |
| 20 days ago | Failed - the request timed out | — |
| 21 days ago | Handshake completed | 426 ms |
| 22 days ago | Handshake completed | 409 ms |
| 23 days ago | Handshake completed | 411 ms |
| 26 days ago | Handshake completed | 382 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 12.
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 DomChecker and makes no claim about it beyond what these checks measured.