Remote MCP · Endpoint

AOPX MCP server

No. AOPX answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.aopx.fr/mcp/

The last check completed an MCP handshake.

Registry name
fr.aopx/aopx
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
266 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.
Listing
From the official MCP registry (active).
Recent checks of AOPX
CheckedResultHandshake
1 hour agoHandshake completed266 ms
2 days agoHandshake completed285 ms
4 days agoHandshake completed124 ms
5 days agoHandshake completed258 ms
7 days agoHandshake completed236 ms
8 days agoHandshake completed280 ms
9 days agoHandshake completed356 ms
12 days agoHandshake completed117 ms
13 days agoHandshake completed219 ms
15 days agoHandshake completed126 ms
16 days agoHandshake completed128 ms
17 days agoHandshake completed198 ms
18 days agoHandshake completed122 ms
19 days agoHandshake completed113 ms
20 days agoHandshake completed112 ms
21 days agoHandshake completed191 ms
22 days agoHandshake completed128 ms

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

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