Remote MCP · Endpoint

io.github.theluckystrike/scope-change MCP server

No. io.github.theluckystrike/scope-change answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mcp.zovo.one/mcp/scope-change

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/scope-change
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
533 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Scope changes against a work order, each with a reason, a date and the client's approval on record.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/scope-change
CheckedResultHandshake
4 hours agoHandshake completed533 ms
1 day agoHandshake completed648 ms
2 days agoHandshake completed177 ms
3 days agoHandshake completed37 ms
4 days agoHandshake completed28 ms
5 days agoHandshake completed21 ms
7 days agoHandshake completed67 ms
9 days agoHandshake completed105 ms
12 days agoHandshake completed42 ms
14 days agoHandshake completed1.33 s
17 days agoHandshake completed173 ms
18 days agoHandshake completed25 ms
21 days agoHandshake completed63 ms
23 days agoHandshake completed35 ms
25 days agoHandshake completed34 ms
26 days agoHandshake completed30 ms
28 days agoHandshake completed37 ms
29 days agoHandshake completed120 ms

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

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 io.github.theluckystrike/scope-change and makes no claim about it beyond what these checks measured.