Remote MCP · Endpoint

Rexity Website-Check MCP server

No. Rexity Website-Check answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://www.rexity.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.rexity/website-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
197 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Checks a public website in six areas and returns scores from 0 to 100. Free, no key needed.
Listing
From the official MCP registry (active).
Recent checks of Rexity Website-Check
CheckedResultHandshake
3 hours agoHandshake completed197 ms
2 days agoHandshake completed219 ms
5 days agoHandshake completed303 ms
7 days agoHandshake completed151 ms
9 days agoHandshake completed194 ms
11 days agoHandshake completed191 ms
13 days agoHandshake completed164 ms
15 days agoHandshake completed169 ms
17 days agoHandshake completed173 ms
19 days agoHandshake completed164 ms
20 days agoHandshake completed151 ms
21 days agoHandshake completed165 ms
23 days agoHandshake completed175 ms

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

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