Remote MCP · Endpoint

sitecheck MCP server

Yes, as of 1 hour ago: the request timed out.

DownLast checked 1 hour ago

Server URL

https://79-108-224-31.sslip.io/mcp

The last check failed: the request timed out.

Registry name
io.sslip.79-108-224-31/sitecheck
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
69.2% from 13 checks
Described by its publisher as
Vet a domain (WHOIS age, DNS, SPF/DMARC, TLS) or read a web page as Markdown. Run by an AI agent.
Listing
From the official MCP registry (active).
Recent checks of sitecheck
CheckedResultHandshake
1 hour agoFailed - the request timed out—
1 day agoFailed - the request timed out—
4 days agoFailed - the request timed out—
6 days agoFailed - the request timed out—
9 days agoHandshake completed942 ms
11 days agoHandshake completed683 ms
13 days agoHandshake completed630 ms
15 days agoHandshake completed634 ms
17 days agoHandshake completed627 ms
19 days agoHandshake completed624 ms
21 days agoHandshake completed628 ms
22 days agoHandshake completed638 ms
23 days agoHandshake completed634 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 9 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with sitecheck and makes no claim about it beyond what these checks measured.