Remote MCP · Endpoint

agmail MCP server

No. agmail answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://agmail.shveik.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.shveik/agmail
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
302 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Email inboxes for agents by the hour: wait for a mail, get the code or link. Pay per call.
Website
https://agmail.shveik.dev/
Listing
From the official MCP registry (active).
Recent checks of agmail
CheckedResultHandshake
57 minutes agoHandshake completed302 ms
1 day agoHandshake completed301 ms
4 days agoHandshake completed294 ms
6 days agoHandshake completed295 ms
9 days agoHandshake completed291 ms
11 days agoHandshake completed297 ms
13 days agoHandshake completed322 ms
15 days agoHandshake completed308 ms
17 days agoHandshake completed296 ms
19 days agoHandshake completed294 ms
21 days agoHandshake completed292 ms
22 days agoHandshake completed303 ms
23 days agoHandshake completed374 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with agmail and makes no claim about it beyond what these checks measured.