Remote MCP · Endpoint

CloudMedico Public MCP MCP server

No. CloudMedico Public MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cloudmedico.com/public-mcp

The last check completed an MCP handshake.

Registry name
com.cloudmedico/public-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
217 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only CloudMedico product information with verified source links.
Listing
From the official MCP registry (active).
Recent checks of CloudMedico Public MCP
CheckedResultHandshake
1 hour agoHandshake completed217 ms
13 hours agoHandshake completed259 ms
2 days agoHandshake completed495 ms
4 days agoHandshake completed212 ms
6 days agoHandshake completed194 ms
9 days agoHandshake completed218 ms
11 days agoHandshake completed641 ms
13 days agoHandshake completed761 ms
15 days agoHandshake completed556 ms
17 days agoHandshake completed469 ms
19 days agoHandshake completed557 ms
21 days agoHandshake completed550 ms
23 days agoHandshake completed523 ms
24 days agoHandshake completed655 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.

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