Remote MCP · Endpoint

AEO Inspector MCP server

No. AEO Inspector answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://aeoinspector.com/mcp

The last check completed an MCP handshake.

Registry name
com.aeoinspector/aeo-inspector
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
329 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AEO scan, 16-engine AI report and one-domain security + AEO report with fixes (x402 USDC).
Listing
From the official MCP registry (active).
Recent checks of AEO Inspector
CheckedResultHandshake
34 minutes agoHandshake completed329 ms
8 days agoHandshake completed283 ms
9 days agoHandshake completed242 ms
11 days agoHandshake completed513 ms
12 days agoHandshake completed333 ms
12 days agoHandshake completed274 ms
14 days agoHandshake completed362 ms
14 days agoHandshake completed99 ms
16 days agoHandshake completed380 ms
19 days agoHandshake completed324 ms
21 days agoHandshake completed694 ms
24 days agoHandshake completed252 ms
26 days agoHandshake completed179 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 AEO Inspector and makes no claim about it beyond what these checks measured.