Remote MCP · Endpoint

Web & domain tools MCP server

No. Web & domain tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fourzerotwo.si/mcp/v/web

The last check completed an MCP handshake.

Registry name
si.fourzerotwo/web
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
201 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read any public page as markdown, link previews, URL safety, page audits, domain availability and…
Listing
From the official MCP registry (active).
Recent checks of Web & domain tools
CheckedResultHandshake
1 hour agoHandshake completed201 ms
1 day agoHandshake completed209 ms
2 days agoHandshake completed212 ms
3 days agoHandshake completed198 ms
4 days agoHandshake completed181 ms
5 days agoHandshake completed197 ms
6 days agoHandshake completed487 ms
9 days agoHandshake completed222 ms
11 days agoHandshake completed198 ms
14 days agoHandshake completed353 ms
16 days agoHandshake completed181 ms
18 days agoHandshake completed185 ms
20 days agoHandshake completed277 ms
22 days agoHandshake completed204 ms
24 days agoHandshake completed201 ms

The last 15 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 Web & domain tools and makes no claim about it beyond what these checks measured.