Remote MCP · Endpoint

Cortex booking MCP server

No. Cortex booking answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://book.enhancedint.com/%7Bbusiness%7D/mcp

The last check completed an MCP handshake.

Registry name
com.enhancedint/cortex-booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
537 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Book with businesses on Cortex: see services, prices and open times, then book. No key needed.
Listing
From the official MCP registry (deprecated).
Recent checks of Cortex booking
CheckedResultHandshake
1 hour agoHandshake completed537 ms
2 days agoHandshake completed593 ms
5 days agoHandshake completed723 ms
7 days agoHandshake completed496 ms
9 days agoHandshake completed525 ms
11 days agoHandshake completed611 ms
13 days agoHandshake completed447 ms
15 days agoHandshake completed770 ms
17 days agoHandshake completed466 ms
19 days agoHandshake completed564 ms
20 days agoHandshake completed2.69 s
21 days agoHandshake completed1.22 s
23 days agoHandshake completed786 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 Cortex booking and makes no claim about it beyond what these checks measured.