Remote MCP · Endpoint
dev.dnsdoctor/dns-doctor MCP server
No. dev.dnsdoctor/dns-doctor answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://dnsdoctor.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.dnsdoctor/dns-doctor
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 429 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 429 ms |
| 2 days ago | Handshake completed | 164 ms |
| 4 days ago | Handshake completed | 367 ms |
| 5 days ago | Handshake completed | 402 ms |
| 7 days ago | Handshake completed | 388 ms |
| 8 days ago | Handshake completed | 554 ms |
| 9 days ago | Handshake completed | 408 ms |
| 12 days ago | Handshake completed | 404 ms |
| 13 days ago | Handshake completed | 363 ms |
| 15 days ago | Handshake completed | 446 ms |
| 16 days ago | Handshake completed | 365 ms |
| 17 days ago | Handshake completed | 360 ms |
| 19 days ago | Handshake completed | 364 ms |
| 19 days ago | Handshake completed | 363 ms |
| 20 days ago | Handshake completed | 390 ms |
| 21 days ago | Handshake completed | 372 ms |
| 22 days ago | Handshake completed | 358 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 dev.dnsdoctor/dns-doctor and makes no claim about it beyond what these checks measured.