Remote MCP · Endpoint

ai.kaiv/dns-check MCP server

No. ai.kaiv/dns-check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.kaiv.ai/api/bridge/mcp/dns-check-e159a722

The last check completed an MCP handshake.

Registry name
ai.kaiv/dns-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
274 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Live DNS lookups for agents: A/MX/TXT/SPF/CNAME/PTR with TTLs and DNSSEC, via Google Public DNS.
Listing
From the official MCP registry (active).
Recent checks of ai.kaiv/dns-check
CheckedResultHandshake
1 hour agoHandshake completed274 ms
1 day agoHandshake completed258 ms
3 days agoHandshake completed172 ms
3 days agoHandshake completed179 ms
4 days agoHandshake completed173 ms
5 days agoHandshake completed183 ms
7 days agoHandshake completed456 ms
10 days agoHandshake completed209 ms
12 days agoHandshake completed254 ms
15 days agoHandshake completed180 ms
17 days agoHandshake completed189 ms
19 days agoHandshake completed207 ms
21 days agoHandshake completed156 ms
23 days agoHandshake completed324 ms
25 days agoHandshake completed149 ms
26 days agoHandshake completed149 ms
28 days agoHandshake completed171 ms
29 days agoHandshake completed189 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 ai.kaiv/dns-check and makes no claim about it beyond what these checks measured.