Remote MCP · Endpoint

entityindex.ai MCP server

No. entityindex.ai answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://entityindex.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.entityindex/entityindex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified hotels in Andorra for AI agents: search by area, spa, pets, ski-in, family; official links.
Listing
From the official MCP registry (active).
Recent checks of entityindex.ai
CheckedResultHandshake
19 minutes agoHandshake completed82 ms
10 days agoHandshake completed152 ms
10 days agoHandshake completed160 ms
11 days agoHandshake completed169 ms
13 days agoHandshake completed141 ms
14 days agoHandshake completed130 ms
14 days agoHandshake completed105 ms
15 days agoHandshake completed102 ms
17 days agoHandshake completed108 ms
19 days agoHandshake completed141 ms
21 days agoHandshake completed94 ms
24 days agoHandshake completed65 ms
26 days agoHandshake completed106 ms
28 days agoHandshake completed92 ms

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

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