Remote MCP · Endpoint

Scopeweb MCP server

No. Scopeweb answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.scopeweb.io/mcp

The last check completed an MCP handshake.

Registry name
io.scopeweb/scopeweb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
223 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Suggest domain names, rank them, confirm availability at the registry, hand over a buy link.
Listing
From the official MCP registry (active).
Recent checks of Scopeweb
CheckedResultHandshake
1 hour agoHandshake completed223 ms
2 days agoHandshake completed169 ms
4 days agoHandshake completed371 ms
6 days agoHandshake completed186 ms
7 days agoHandshake completed316 ms
8 days agoHandshake completed183 ms
9 days agoHandshake completed662 ms
12 days agoHandshake completed209 ms
13 days agoHandshake completed505 ms
15 days agoHandshake completed184 ms
17 days agoHandshake completed304 ms
18 days agoHandshake completed159 ms
19 days agoHandshake completed175 ms
20 days agoHandshake completed330 ms
21 days agoHandshake completed202 ms
21 days agoHandshake completed394 ms
23 days agoHandshake completed167 ms

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

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