Remote MCP · Endpoint

EmailMCP MCP server

No. EmailMCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.setip.io/mcp

The last check completed an MCP handshake.

Registry name
io.setip/emailmcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
28 ms
Tools exposed
56 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI agent email — 23 tools free to read inbox, 28 paid to send. $9.99/mo. Token auto-provisioned.
Listing
From the official MCP registry (active).
Recent checks of EmailMCP
CheckedResultHandshake
1 hour agoHandshake completed28 ms
9 days agoHandshake completed37 ms
10 days agoHandshake completed67 ms
11 days agoHandshake completed31 ms
12 days agoHandshake completed166 ms
14 days agoHandshake completed35 ms
14 days agoHandshake completed27 ms
15 days agoHandshake completed33 ms
17 days agoHandshake completed27 ms
19 days agoHandshake completed28 ms
21 days agoHandshake completed31 ms
24 days agoHandshake completed44 ms
26 days agoHandshake completed37 ms
28 days agoHandshake completed27 ms

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

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