Remote MCP · Endpoint
Mailvett: Email Validation API for AI Agents MCP server
No. Mailvett: Email Validation API for AI Agents answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry
The last check completed an MCP handshake.
- Registry name
- io.github.CyberMax-tools/email-validate
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 174 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 93.3% from 15 checks
- Described by its publisher as
- Mailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 174 ms |
| 1 day ago | Handshake completed | 97 ms |
| 3 days ago | Handshake completed | 108 ms |
| 6 days ago | Handshake completed | 94 ms |
| 7 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Handshake completed | 80 ms |
| 10 days ago | Handshake completed | 174 ms |
| 11 days ago | Handshake completed | 111 ms |
| 13 days ago | Handshake completed | 101 ms |
| 15 days ago | Handshake completed | 109 ms |
| 17 days ago | Handshake completed | 137 ms |
| 19 days ago | Handshake completed | 600 ms |
| 20 days ago | Handshake completed | 71 ms |
| 21 days ago | Handshake completed | 63 ms |
| 22 days ago | Handshake completed | 63 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Mailvett: Email Validation API for AI Agents and makes no claim about it beyond what these checks measured.