Remote MCP · Endpoint

PetCare Atlas MCP server

No. PetCare Atlas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://petcareatlas.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.petcareatlas/atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
531 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find UK vets and pet-care providers, and what practices and retailers charge.
Listing
From the official MCP registry (active).
Recent checks of PetCare Atlas
CheckedResultHandshake
1 hour agoHandshake completed531 ms
1 day agoHandshake completed923 ms
4 days agoHandshake completed566 ms
6 days agoHandshake completed529 ms
7 days agoHandshake completed507 ms
9 days agoHandshake completed507 ms
10 days agoHandshake completed443 ms
11 days agoHandshake completed509 ms
14 days agoHandshake completed522 ms
15 days agoHandshake completed517 ms
17 days agoHandshake completed516 ms
18 days agoHandshake completed515 ms
20 days agoHandshake completed531 ms
21 days agoHandshake completed1.29 s
22 days agoHandshake completed537 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 PetCare Atlas and makes no claim about it beyond what these checks measured.