Remote MCP · Endpoint
SEO·AEO·GEO MCP server
No. SEO·AEO·GEO answered an MCP handshake 14 minutes ago.
UpLast checked 14 minutes ago
Server URL
https://seoaeogeo.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.seoaeogeo/seo-aeo-geo
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 136 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 85.7% from 14 checks
- Described by its publisher as
- Audit a page for Google and AI search (ChatGPT, Claude, Perplexity); get a fix pack to apply.
- Website
- https://seoaeogeo.app/agents
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 14 minutes ago | Handshake completed | 136 ms |
| 10 days ago | Handshake completed | 118 ms |
| 10 days ago | Handshake completed | 4.94 s |
| 11 days ago | Handshake completed | 5.78 s |
| 13 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Handshake completed | 4.81 s |
| 15 days ago | Handshake completed | 5.01 s |
| 17 days ago | Handshake completed | 529 ms |
| 19 days ago | Handshake completed | 4.86 s |
| 21 days ago | Handshake completed | 515 ms |
| 24 days ago | Handshake completed | 289 ms |
| 26 days ago | Handshake completed | 4.59 s |
| 28 days ago | Handshake completed | 4.42 s |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 15.
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 SEO·AEO·GEO and makes no claim about it beyond what these checks measured.