Remote MCP · Endpoint
Booking Request MCP server
No. Booking Request answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://bonissystems.com/api/knox/agents/booking-request/mcp
The last check completed an MCP handshake.
- Registry name
- com.bonissystems/booking-request
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 173 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 173 ms |
| 1 day ago | Handshake completed | 168 ms |
| 3 days ago | Handshake completed | 137 ms |
| 3 days ago | Handshake completed | 151 ms |
| 4 days ago | Handshake completed | 133 ms |
| 5 days ago | Handshake completed | 166 ms |
| 7 days ago | Handshake completed | 132 ms |
| 10 days ago | Handshake completed | 130 ms |
| 12 days ago | Handshake completed | 116 ms |
| 14 days ago | Handshake completed | 156 ms |
| 17 days ago | Handshake completed | 143 ms |
| 19 days ago | Handshake completed | 458 ms |
| 21 days ago | Handshake completed | 172 ms |
| 23 days ago | Handshake completed | 175 ms |
| 25 days ago | Handshake completed | 117 ms |
| 26 days ago | Handshake completed | 611 ms |
| 28 days ago | Handshake completed | 150 ms |
| 29 days ago | Handshake completed | 174 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Booking Request and makes no claim about it beyond what these checks measured.