Remote MCP · Endpoint

MediMo MCP server

No. MediMo answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://medimo.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.medimo/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find and book UK private physiotherapy, osteopathy and chiropractic clinics, with live availability.
Listing
From the official MCP registry (active).
Recent checks of MediMo
CheckedResultHandshake
3 hours agoHandshake completed151 ms
2 days agoHandshake completed171 ms
4 days agoHandshake completed152 ms
5 days agoHandshake completed143 ms
7 days agoHandshake completed149 ms
8 days agoHandshake completed169 ms
9 days agoHandshake completed182 ms
12 days agoHandshake completed133 ms
13 days agoHandshake completed222 ms
15 days agoHandshake completed171 ms
16 days agoHandshake completed154 ms
17 days agoHandshake completed151 ms
18 days agoHandshake completed149 ms
19 days agoHandshake completed137 ms
20 days agoHandshake completed152 ms
21 days agoHandshake completed191 ms
22 days agoHandshake completed487 ms

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

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