Remote MCP · Endpoint

SiteCheck Health & Travel MCP server

No. SiteCheck Health & Travel answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://api.healthtravel-api.workers.dev/mcp?ref=registry

The last check completed an MCP handshake.

Registry name
io.github.bck-stack/sitecheck-health-travel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
121 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
121 pay-per-call agent tools: health care, drug, provider and travel data tools. x402
Listing
From the official MCP registry (active).
Recent checks of SiteCheck Health & Travel
CheckedResultHandshake
17 hours agoHandshake completed59 ms
11 days agoHandshake completed46 ms
12 days agoHandshake completed104 ms
12 days agoHandshake completed280 ms
14 days agoHandshake completed264 ms
15 days agoHandshake completed51 ms
16 days agoHandshake completed232 ms
17 days agoHandshake completed227 ms
18 days agoHandshake completed274 ms
20 days agoHandshake completed438 ms
22 days agoHandshake completed233 ms
25 days agoHandshake completed474 ms

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

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