Remote MCP · Endpoint

Voidmail (hosted) MCP server

No. Voidmail (hosted) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.voidly.ai/mcp/mail

The last check completed an MCP handshake.

Registry name
io.github.voidly-ai/voidmail
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
698 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hosted agent inboxes: read mail, send to owner-approved recipients. Mail is server-readable.
Listing
From the official MCP registry (active).
Recent checks of Voidmail (hosted)
CheckedResultHandshake
1 hour agoHandshake completed698 ms
4 days agoHandshake completed835 ms
14 days agoHandshake completed613 ms
15 days agoHandshake completed846 ms
15 days agoHandshake completed1.44 s
17 days agoHandshake completed704 ms
18 days agoHandshake completed473 ms
19 days agoHandshake completed602 ms
20 days agoHandshake completed535 ms
21 days agoHandshake completed872 ms
23 days agoHandshake completed704 ms
25 days agoHandshake completed1.15 s
28 days agoHandshake completed548 ms

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

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