Remote MCP · Endpoint

DMARC Shark — Email DNS Checker MCP server

Yes, as of 6 days ago: the request timed out.

DownLast checked 6 days ago

Server URL

https://dmarcshark.com/mcp

The last check failed: the request timed out.

Registry name
com.dmarcshark/email-dns-checker
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Check a domain's public SPF, DMARC, MX and DKIM DNS records on demand. No account required.
Listing
From the official MCP registry (active).
Recent checks of DMARC Shark — Email DNS Checker
CheckedResultHandshake
6 days agoFailed - the request timed out—
7 days agoFailed - the request timed out—
7 days agoHandshake completed299 ms
9 days agoHandshake completed331 ms
10 days agoHandshake completed314 ms
11 days agoHandshake completed300 ms
12 days agoHandshake completed313 ms
13 days agoHandshake completed317 ms
15 days agoHandshake completed308 ms
17 days agoHandshake completed318 ms
20 days agoHandshake completed319 ms
22 days agoHandshake completed305 ms
24 days agoHandshake completed299 ms

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

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 DMARC Shark — Email DNS Checker and makes no claim about it beyond what these checks measured.