Remote MCP · Endpoint

ScopeAI GEO Observation MCP server

No. ScopeAI GEO Observation answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://scopeai.cc/mcp

The last check completed an MCP handshake.

Registry name
cc.scopeai/geo-observation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.85 s
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
GEO brand visibility and AI citation evidence. Free capability discovery and request matching.
Listing
From the official MCP registry (active).
Recent checks of ScopeAI GEO Observation
CheckedResultHandshake
57 minutes agoHandshake completed1.85 s
13 hours agoHandshake completed1.70 s
1 day agoHandshake completed101 ms
2 days agoHandshake completed1.09 s
4 days agoHandshake completed401 ms
7 days agoHandshake completed1.30 s
9 days agoHandshake completed119 ms
12 days agoHandshake completed79 ms
14 days agoHandshake completed2.31 s
16 days agoHandshake completed1.42 s
18 days agoHandshake completed1.27 s
20 days agoHandshake completed1.43 s
22 days agoHandshake completed66 ms
23 days agoHandshake completed102 ms

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

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