Remote MCP · Endpoint

MoveSurge MCP server

No. MoveSurge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://movesurge.com/mcp

The last check completed an MCP handshake.

Registry name
com.movesurge/movesurge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
368 ms
Tools exposed
13 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Market news with the measured price reaction attached to the event that caused it.
Listing
From the official MCP registry (active).
Recent checks of MoveSurge
CheckedResultHandshake
1 hour agoHandshake completed368 ms
8 days agoFailed - the check failed for an unclassified reason—
9 days agoHandshake completed343 ms
11 days agoHandshake completed164 ms
12 days agoHandshake completed355 ms
12 days agoHandshake completed365 ms
14 days agoHandshake completed358 ms
14 days agoHandshake completed485 ms
16 days agoHandshake completed341 ms
19 days agoHandshake completed363 ms
21 days agoHandshake completed359 ms
24 days agoHandshake completed347 ms
26 days agoHandshake completed448 ms
28 days agoFailed - the server returned an HTTP error—

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

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