Remote MCP · Endpoint

Domain Health MCP server

No. Domain Health answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.modernmustardseed.com/domain-health

The last check completed an MCP handshake.

Registry name
com.modernmustardseed/domain-health
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Domain checks: SPF, DKIM, DMARC, BIMI, MTA-STS, SSL/TLS and HTTP security headers.
Listing
From the official MCP registry (active).
Recent checks of Domain Health
CheckedResultHandshake
1 hour agoHandshake completed185 ms
1 day agoHandshake completed98 ms
2 days agoHandshake completed48 ms
3 days agoHandshake completed80 ms
4 days agoHandshake completed68 ms
5 days agoHandshake completed90 ms
6 days agoHandshake completed84 ms
9 days agoHandshake completed78 ms
11 days agoHandshake completed83 ms
14 days agoHandshake completed81 ms
16 days agoHandshake completed76 ms
18 days agoHandshake completed62 ms
20 days agoHandshake completed87 ms
22 days agoHandshake completed80 ms
24 days agoHandshake completed72 ms

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

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 Domain Health and makes no claim about it beyond what these checks measured.