Remote MCP · Endpoint

AimRank MCP server

No. AimRank answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.aimrank.io/mcp/public

The last check completed an MCP handshake.

Registry name
io.aimrank/aimrank
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read public pairwise-preference rankings and their statistical quality evidence. No API key.
Listing
From the official MCP registry (active).
Recent checks of AimRank
CheckedResultHandshake
1 hour agoHandshake completed292 ms
2 days agoHandshake completed290 ms
4 days agoHandshake completed291 ms
5 days agoHandshake completed290 ms
7 days agoHandshake completed297 ms
8 days agoHandshake completed293 ms
9 days agoHandshake completed288 ms
12 days agoHandshake completed294 ms
13 days agoHandshake completed296 ms
15 days agoHandshake completed293 ms
16 days agoHandshake completed293 ms
18 days agoHandshake completed293 ms
19 days agoHandshake completed297 ms
20 days agoHandshake completed299 ms
20 days agoHandshake completed288 ms
21 days agoHandshake completed290 ms
22 days agoHandshake completed311 ms

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

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