Remote MCP · Endpoint

listme.name rankings MCP server

No. listme.name rankings answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://listme.name/mcp

The last check completed an MCP handshake.

Registry name
io.github.yunusemrejr/listme
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
573 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only ranked lists, product facts, alternatives and comparisons for software, apps and books.
Listing
From the official MCP registry (active).
Recent checks of listme.name rankings
CheckedResultHandshake
14 minutes agoHandshake completed573 ms
9 days agoHandshake completed508 ms
9 days agoHandshake completed414 ms
11 days agoHandshake completed584 ms
12 days agoHandshake completed335 ms
13 days agoHandshake completed630 ms
14 days agoHandshake completed693 ms
14 days agoHandshake completed344 ms
16 days agoHandshake completed771 ms
19 days agoHandshake completed508 ms
21 days agoHandshake completed384 ms
24 days agoHandshake completed381 ms
26 days agoHandshake completed603 ms
28 days agoHandshake completed590 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 listme.name rankings and makes no claim about it beyond what these checks measured.