Remote MCP · Endpoint

Email Check MCP server

No. Email Check answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://email-check.david-cyr.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Dawaxwx/email-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
763 ms
Tools exposed
1 tool
Uptime, last 30 days
58.8% from 17 checks
Described by its publisher as
Fast email validation at the edge: syntax, MX records, disposable-domain detection.
Listing
From the official MCP registry (active).
Recent checks of Email Check
CheckedResultHandshake
2 hours agoHandshake completed763 ms
2 days agoHandshake completed676 ms
4 days agoHandshake completed376 ms
5 days agoHandshake completed46 ms
7 days agoHandshake completed565 ms
8 days agoHandshake completed733 ms
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed1.50 s
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed1.03 s
20 days agoHandshake completed804 ms
21 days agoHandshake completed894 ms
23 days agoFailed - the server returned an HTTP error—

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

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