Remote MCP · Endpoint

Shiftmoor MCP server

No. Shiftmoor answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://shiftmoor.cybermaxtools.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/shiftmoor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
83 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Website change monitor MCP: see what changed on any public page. Free 3 pages; $4.99/mo.
Listing
From the official MCP registry (active).
Recent checks of Shiftmoor
CheckedResultHandshake
3 hours agoHandshake completed83 ms
13 hours agoHandshake completed81 ms
2 days agoHandshake completed123 ms
4 days agoHandshake completed74 ms
7 days agoHandshake completed51 ms
9 days agoHandshake completed151 ms
11 days agoHandshake completed124 ms
14 days agoHandshake completed96 ms
15 days agoHandshake completed128 ms
18 days agoHandshake completed83 ms
20 days agoHandshake completed54 ms
21 days agoHandshake completed88 ms
23 days agoHandshake completed96 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 Shiftmoor and makes no claim about it beyond what these checks measured.