Remote MCP · Endpoint

Review Times MCP server

No. Review Times answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://reviewtimes.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.reviewtimes/review-times
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Live review times for AI app stores: ChatGPT, Claude, Muse, Grok, Cursor. Check before you submit.
Listing
From the official MCP registry (active).
Recent checks of Review Times
CheckedResultHandshake
1 hour agoHandshake completed49 ms
2 days agoHandshake completed118 ms
4 days agoHandshake completed152 ms
6 days agoHandshake completed95 ms
7 days agoHandshake completed60 ms
9 days agoHandshake completed150 ms
10 days agoHandshake completed328 ms
11 days agoHandshake completed184 ms
14 days agoHandshake completed109 ms
15 days agoHandshake completed125 ms
17 days agoHandshake completed126 ms
18 days agoHandshake completed157 ms
19 days agoHandshake completed83 ms
21 days agoHandshake completed85 ms
22 days agoHandshake completed89 ms
22 days agoHandshake completed105 ms

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

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