Remote MCP · Endpoint

Email DNS Preflight x402 MCP server

No. Email DNS Preflight x402 answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://email-dns-preflight-x402.copper-crate.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.rosarioV25/email-dns-preflight-x402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paid email, DNS, mail-security and RDAP intelligence for agents over x402.
Listing
From the official MCP registry (active).
Recent checks of Email DNS Preflight x402
CheckedResultHandshake
5 hours agoHandshake completed160 ms
9 days agoHandshake completed123 ms
10 days agoHandshake completed207 ms
11 days agoHandshake completed369 ms
12 days agoHandshake completed396 ms
14 days agoHandshake completed262 ms
14 days agoHandshake completed200 ms
15 days agoHandshake completed184 ms
17 days agoHandshake completed145 ms
19 days agoHandshake completed272 ms
22 days agoHandshake completed184 ms
24 days agoHandshake completed188 ms
26 days agoHandshake completed183 ms
28 days agoHandshake completed178 ms

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

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 Email DNS Preflight x402 and makes no claim about it beyond what these checks measured.