Connect AOPX and your agent gets 4 tools, among them public_outcomes, public_stats, recommend_provider. It answers at https://api.aopx.fr/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 3 of 4 times since 23 September 2026; the last check, on 7 November 2026, succeeded.
Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
public_outcomes | Read recent caller-reported production outcomes from the AOPX public evidence surface. Use this to inspect what was reported after real recommendations were executed, not to request a new recommendation. Provider identities are exposed only Inputs: limit |
public_stats | Read aggregate public statistics from the AOPX production pilot, including consultation and reported-outcome activity. Use this for public telemetry, not for provider recommendation. LAB benchmarks, tests, shadow runs and replay events are |
recommend_provider | Use when a software agent needs an AOPX recommendation for the SEARCH category instead of hard-coding a single supported provider. Supported modes are ECONOMY and CRITICAL. Returns a primary provider and, when applicable, a fallback provide Inputs: mode, client_id, max_cost_eur, max_latency_ms |
report_outcome | Use only after a real external execution of a provider path returned by recommend_provider. Records the caller-reported production outcome for that recommendation_id. The recommendation must exist, only one outcome is accepted per recommend Inputs: recommendation_id, attempts |
Every block below points at https://api.aopx.fr/mcp/. Pick your client and copy.
claude mcp add --transport http aopx https://api.aopx.fr/mcp/
{
"mcpServers": {
"aopx": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.aopx.fr/mcp/"]
}
}
}{
"mcpServers": {
"aopx": {
"url": "https://api.aopx.fr/mcp/"
}
}
}{
"servers": {
"aopx": {
"type": "http",
"url": "https://api.aopx.fr/mcp/"
}
}
}{
"context_servers": {
"aopx": {
"url": "https://api.aopx.fr/mcp/"
}
}
}{
"mcpServers": {
"aopx": {
"serverUrl": "https://api.aopx.fr/mcp/"
}
}
}{
"mcpServers": {
"aopx": {
"url": "https://api.aopx.fr/mcp/"
}
}
}name: AOPX
version: 0.0.1
schema: v1
mcpServers:
- name: AOPX
type: streamable-http
url: https://api.aopx.fr/mcp/{
"mcpServers": {
"aopx": {
"httpUrl": "https://api.aopx.fr/mcp/"
}
}
}{
"mcpServers": {
"aopx": {
"type": "http",
"url": "https://api.aopx.fr/mcp/"
}
}
}{
"mcpServers": {
"aopx": {
"url": "https://api.aopx.fr/mcp/"
}
}
}goose://extension?url=https%3A%2F%2Fapi.aopx.fr%2Fmcp%2F&type=streamable_http&id=aopx&name=AOPX
It answered our last check on 7 November 2026 in 93 ms. Over 4 checks since 23 September 2026 it answered 3. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by aopx.fr and served from api.aopx.fr, the vendor's own domain: https://api.aopx.fr/mcp/.
4, as returned by the server's own tools/list on 13 November 2026: public_outcomes, public_stats, recommend_provider, report_outcome.
It answered our last check on 7 November 2026 in 93 ms. Over 4 checks since 23 September 2026 it answered 3.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.aopx.fr/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: fr.aopx. Endpoint host: api.aopx.fr. ARD identifier: urn:air:fr.aopx:mcp:aopx.
First indexed 22 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.