Remote MCP · Endpoint

CMeIn MCP server

No. CMeIn answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.cmein.com/mcp

The last check completed an MCP handshake.

Registry name
com.cmein/cmein
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Turns ordinary phone photos of you into photos of you having a life. Advice, credits, 4,500 scenes.
Listing
From the official MCP registry (active).
Recent checks of CMeIn
CheckedResultHandshake
2 hours agoHandshake completed129 ms
2 days agoHandshake completed130 ms
4 days agoHandshake completed210 ms
7 days agoHandshake completed171 ms
9 days agoHandshake completed130 ms
11 days agoHandshake completed147 ms
13 days agoHandshake completed134 ms
15 days agoHandshake completed173 ms
16 days agoHandshake completed150 ms
18 days agoHandshake completed201 ms
19 days agoHandshake completed139 ms
20 days agoHandshake completed158 ms
23 days agoHandshake completed204 ms
24 days agoHandshake completed486 ms

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

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