Remote MCP · Endpoint

dev.dnsdoctor/dns-doctor MCP server

No. dev.dnsdoctor/dns-doctor answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
174 ms
Tools exposed
29 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes.
Website
https://dnsdoctor.dev/methodology
Repository
https://github.com/dnsdoctor/claude-plugin
Listing
From the official MCP registry (active).
Recent checks of dev.dnsdoctor/dns-doctor
CheckedResultHandshake
1 hour agoHandshake completed174 ms
1 day agoHandshake completed514 ms
3 days agoHandshake completed375 ms
3 days agoHandshake completed394 ms
4 days agoHandshake completed391 ms
5 days agoHandshake completed378 ms
7 days agoHandshake completed156 ms
10 days agoHandshake completed397 ms
12 days agoHandshake completed407 ms
15 days agoHandshake completed391 ms
17 days agoHandshake completed378 ms
19 days agoHandshake completed443 ms
21 days agoHandshake completed429 ms
23 days agoHandshake completed164 ms
25 days agoHandshake completed367 ms
26 days agoHandshake completed402 ms
28 days agoHandshake completed388 ms
29 days agoHandshake completed554 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.