Remote MCP · Endpoint

Hotel Fact Graph MCP server

No. Hotel Fact Graph answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://hotels.isitabizday.com/mcp

The last check completed an MCP handshake.

Registry name
com.isitabizday/hotel-fact-graph
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Dated, cited hotel facts from hotels' own sites and official registers, Portugal and Spain.
Listing
From the official MCP registry (active).
Recent checks of Hotel Fact Graph
CheckedResultHandshake
35 minutes agoHandshake completed291 ms
9 days agoHandshake completed288 ms
10 days agoHandshake completed345 ms
11 days agoHandshake completed299 ms
12 days agoHandshake completed372 ms
14 days agoHandshake completed358 ms
14 days agoHandshake completed304 ms
15 days agoHandshake completed302 ms
17 days agoHandshake completed300 ms
19 days agoHandshake completed303 ms
21 days agoHandshake completed298 ms
24 days agoHandshake completed309 ms
26 days agoHandshake completed291 ms

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

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