Remote MCP · Endpoint
kz.tehprof.booking/reservations MCP server
No. kz.tehprof.booking/reservations answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://booking.tehprof.kz/mcp
The last check completed an MCP handshake.
- Registry name
- kz.tehprof.booking/reservations
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 579 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 94.7% from 19 checks
- Described by its publisher as
- Remote MCP for TehProf Booking: browse resources & availability, create & cancel reservations.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 579 ms |
| 10 hours ago | Handshake completed | 550 ms |
| 1 day ago | Handshake completed | 562 ms |
| 2 days ago | Handshake completed | 543 ms |
| 4 days ago | Handshake completed | 519 ms |
| 4 days ago | Handshake completed | 730 ms |
| 5 days ago | Handshake completed | 536 ms |
| 6 days ago | Handshake completed | 512 ms |
| 8 days ago | Failed - the connection was refused or dropped | — |
| 11 days ago | Handshake completed | 517 ms |
| 13 days ago | Handshake completed | 514 ms |
| 16 days ago | Handshake completed | 511 ms |
| 18 days ago | Handshake completed | 503 ms |
| 20 days ago | Handshake completed | 538 ms |
| 22 days ago | Handshake completed | 507 ms |
| 24 days ago | Handshake completed | 842 ms |
| 26 days ago | Handshake completed | 539 ms |
| 27 days ago | Handshake completed | 546 ms |
| 29 days ago | Handshake completed | 535 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 31.
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 kz.tehprof.booking/reservations and makes no claim about it beyond what these checks measured.