Remote MCP · Endpoint

Beds24 MCP by usefulapi MCP server

Yes, as of 4 hours ago: the server returned an HTTP error.

DownLast checked 4 hours ago

Server URL

https://beds24.usefulapi.io/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.usefulapi/beds24
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
18 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Check bookings, quote stays, read guest messages and reviews, and update calendars in Beds24.
Listing
From the official MCP registry (active).
Recent checks of Beds24 MCP by usefulapi
CheckedResultHandshake
4 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed402 ms
4 days agoHandshake completed205 ms
6 days agoHandshake completed155 ms
8 days agoHandshake completed95 ms
10 days agoHandshake completed215 ms
12 days agoHandshake completed320 ms
14 days agoHandshake completed176 ms
15 days agoHandshake completed207 ms
16 days agoHandshake completed313 ms
18 days agoHandshake completed266 ms
20 days agoHandshake completed185 ms
22 days agoHandshake completed234 ms
24 days agoHandshake completed271 ms

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

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