Remote MCP · Endpoint

Citead GEO Score MCP server

No. Citead GEO Score answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.citead.com/public/mcp/

The last check completed an MCP handshake.

Registry name
com.citead/score
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
305 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free GEO score of a web page or text: how easily AI assistants can quote it, with fixes. No key.
Listing
From the official MCP registry (active).
Recent checks of Citead GEO Score
CheckedResultHandshake
2 hours agoHandshake completed305 ms
10 days agoHandshake completed284 ms
11 days agoHandshake completed279 ms
11 days agoHandshake completed310 ms
13 days agoHandshake completed324 ms
14 days agoHandshake completed292 ms
15 days agoHandshake completed290 ms
16 days agoHandshake completed547 ms
17 days agoHandshake completed289 ms
19 days agoHandshake completed279 ms
22 days agoHandshake completed279 ms
24 days agoHandshake completed307 ms
26 days agoHandshake completed283 ms
29 days agoHandshake completed284 ms

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

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