Remote MCP · Endpoint

Cherami MCP server

No. Cherami answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cherami.to/mcp

The last check completed an MCP handshake.

Registry name
io.github.cherami-mail/cherami-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Email inboxes for recurring agent work. Read, search, reply, draft and organize correspondence.
Website
https://cherami.to/docs/mcp
Listing
From the official MCP registry (active).
Recent checks of Cherami
CheckedResultHandshake
1 hour agoHandshake completed124 ms
2 days agoHandshake completed311 ms
5 days agoHandshake completed255 ms
7 days agoHandshake completed794 ms
9 days agoHandshake completed273 ms
11 days agoHandshake completed285 ms
13 days agoHandshake completed483 ms
15 days agoHandshake completed301 ms
17 days agoHandshake completed293 ms
19 days agoHandshake completed79 ms
20 days agoHandshake completed521 ms
21 days agoHandshake completed304 ms
23 days agoHandshake completed75 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 Cherami and makes no claim about it beyond what these checks measured.