Remote MCP · Endpoint

MCP Rating MCP server

No. MCP Rating answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://mcprating.io/mcp/

The last check completed an MCP handshake.

Registry name
io.mcprating/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
496 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search MCP servers, with our own start-test results, required keys, tools and token cost.
Listing
From the official MCP registry (active).
Recent checks of MCP Rating
CheckedResultHandshake
18 minutes agoHandshake completed496 ms
10 days agoHandshake completed482 ms
10 days agoHandshake completed609 ms
11 days agoHandshake completed507 ms
12 days agoHandshake completed468 ms
14 days agoHandshake completed494 ms
14 days agoHandshake completed477 ms
15 days agoHandshake completed480 ms
17 days agoHandshake completed493 ms
19 days agoHandshake completed481 ms
21 days agoHandshake completed519 ms
24 days agoHandshake completed488 ms
26 days agoHandshake completed562 ms
28 days agoHandshake completed486 ms

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

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