Remote MCP · Endpoint

AI Benchmark Index MCP server

No. AI Benchmark Index answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://aibenchmarkindex.com/mcp

The last check completed an MCP handshake.

Registry name
com.aibenchmarkindex/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
340 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search 264 AI benchmarks by category, with data sources and licences for each.
Listing
From the official MCP registry (active).
Recent checks of AI Benchmark Index
CheckedResultHandshake
5 hours agoHandshake completed340 ms
9 days agoHandshake completed154 ms
10 days agoHandshake completed137 ms
11 days agoHandshake completed191 ms
12 days agoHandshake completed410 ms
14 days agoHandshake completed93 ms
14 days agoHandshake completed149 ms
15 days agoHandshake completed374 ms
17 days agoHandshake completed756 ms
19 days agoHandshake completed161 ms
21 days agoHandshake completed3.27 s
24 days agoHandshake completed167 ms
26 days agoHandshake completed141 ms
28 days agoHandshake completed135 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 AI Benchmark Index and makes no claim about it beyond what these checks measured.