Remote MCP · Endpoint

Inside Airbnb MCP server

No. Inside Airbnb answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/inside-airbnb/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/inside-airbnb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
inside-airbnb -- short-term rental listings by city (fleet #2973).
Listing
From the official MCP registry (active).
Recent checks of Inside Airbnb
CheckedResultHandshake
42 minutes agoHandshake completed60 ms
9 days agoHandshake completed147 ms
10 days agoHandshake completed90 ms
11 days agoHandshake completed93 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed124 ms
14 days agoHandshake completed104 ms
15 days agoHandshake completed98 ms
17 days agoHandshake completed181 ms
19 days agoHandshake completed206 ms
21 days agoHandshake completed104 ms
24 days agoHandshake completed72 ms
26 days agoHandshake completed55 ms
28 days agoHandshake completed59 ms

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

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