Remote MCP · Endpoint

Cooper Email MCP server

No. Cooper Email answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cooperemail.com/mcp

The last check completed an MCP handshake.

Registry name
com.cooperemail/cooper-email
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
137 ms
Tools exposed
79 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Email inboxes for AI agents: send, receive, search, drafts with owner approval, and webhooks.
Listing
From the official MCP registry (active).
Recent checks of Cooper Email
CheckedResultHandshake
1 hour agoHandshake completed137 ms
2 days agoHandshake completed130 ms
4 days agoHandshake completed86 ms
6 days agoHandshake completed93 ms
8 days agoHandshake completed141 ms
10 days agoHandshake completed139 ms
11 days agoHandshake completed75 ms
13 days agoHandshake completed109 ms
14 days agoHandshake completed81 ms
15 days agoHandshake completed101 ms
18 days agoHandshake completed124 ms
19 days agoHandshake completed86 ms
21 days agoHandshake completed65 ms
22 days agoHandshake completed71 ms
23 days agoHandshake completed101 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 Cooper Email and makes no claim about it beyond what these checks measured.