Remote MCP · Endpoint

All4Clinic MCP server

No. All4Clinic answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.all4clinic.com.br/mcp

The last check completed an MCP handshake.

Registry name
br.com.all4clinic/clinic-software
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Help guides, plans and demo booking for All4Clinic, the clinic management software used in Brazil
Listing
From the official MCP registry (active).
Recent checks of All4Clinic
CheckedResultHandshake
2 hours agoHandshake completed71 ms
1 day agoHandshake completed86 ms
2 days agoHandshake completed107 ms
3 days agoHandshake completed110 ms
4 days agoHandshake completed106 ms
5 days agoHandshake completed103 ms
7 days agoHandshake completed103 ms
9 days agoHandshake completed84 ms
12 days agoHandshake completed264 ms
14 days agoHandshake completed105 ms
16 days agoHandshake completed95 ms
18 days agoHandshake completed79 ms
20 days agoHandshake completed633 ms
22 days agoHandshake completed156 ms
24 days agoHandshake completed177 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 All4Clinic and makes no claim about it beyond what these checks measured.