# AOPX (remote · api.aopx.fr)

Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `api.aopx.fr`: 82/100 (this document), [markdown](https://verifymcp.io/servers/fr-aopx-aopx/api.md), [page](https://verifymcp.io/servers/fr-aopx-aopx/api)

## Channel facts

- Endpoint: `https://api.aopx.fr/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 496 tokens (~124/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the AOPX MCP server?

AOPX is a hosted endpoint at https://api.aopx.fr/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http fr-aopx-aopx 'https://api.aopx.fr/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-aopx-aopx": {
      "url": "https://api.aopx.fr/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-aopx-aopx": {
      "type": "http",
      "url": "https://api.aopx.fr/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-aopx-aopx]
url = "https://api.aopx.fr/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-aopx-aopx": {
      "type": "remote",
      "url": "https://api.aopx.fr/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-aopx-aopx --url 'https://api.aopx.fr/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-aopx-aopx:
    url: "https://api.aopx.fr/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-aopx-aopx": {
      "Transport": "http",
      "Url": "https://api.aopx.fr/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-aopx-aopx -t streamable-http -u 'https://api.aopx.fr/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "fr-aopx-aopx": {
      "type": "http",
      "url": "https://api.aopx.fr/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-10-21 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 67. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 77, +3)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 60. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-03 (score 74, +2)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.37

## MCP tools (4)

### `recommend_provider` (~152 tokens)

Recommend a search 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 provider plus a recommendation_id. AOPX does not execute the search and does not handle payment; the caller executes the provider path externally. After a real execution, call report_outcome with the same recommendation_id. max_cost_eur and max_latency_ms are accepted and recorded by the current v0 interface but are not enforced as hard routing constraints.

Input parameters:

- `client_id`
- `max_cost_eur`
- `max_latency_ms`
- `mode` (string, required)

### `report_outcome` (~97 tokens)

Report a production 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 recommendation, and provider attempts must match the recommended primary/fallback path. Reported outcomes are production evidence supplied by the caller; they are not described as independently verified outcomes.

Input parameters:

- `attempts` (array, required)
- `recommendation_id` (string, required)

### `public_stats` (~56 tokens)

Get public AOPX statistics

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 excluded from these production statistics.

### `public_outcomes` (~86 tokens)

Get recent public AOPX 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 through public aliases. LAB benchmarks, tests, shadow runs and replays are not returned here, and reported outcomes are not described as independently verified.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fr-aopx-aopx/api#diagnostics

## Score history

- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-04: 74
- 2026-10-03: 74
- 2026-10-02: 72
- 2026-10-01: 72
- 2026-09-30: 72
- 2026-09-29: 72
- 2026-09-28: 71
- 2026-09-27: 64
- 2026-09-26: 62
- 2026-09-25: 62
- 2026-09-24: 62
- 2026-09-23: 61
- 2026-09-22: 61

## Common questions

### What is the AOPX MCP server?

AOPX is an MCP server listed in the public MCP registry as fr.aopx/aopx. Selects between supported SEARCH providers for ECONOMY or CRITICAL mode. This page covers its hosted endpoint (https://api.aopx.fr/mcp/).

### Is the AOPX MCP server safe to use?

AOPX scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AOPX MCP server expose?

AOPX exposes 4 tools: recommend_provider, report_outcome, public_stats, public_outcomes. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.

### Does the AOPX MCP server require authentication?

No. We connected to AOPX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AOPX MCP server still maintained?

AOPX is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.aopx.fr/mcp/
- Website: https://aopx.fr/
- Changelog RSS feed: https://verifymcp.io/servers/fr-aopx-aopx/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-aopx-aopx/api.json
- HTML version of this page: https://verifymcp.io/servers/fr-aopx-aopx/api