Search excessionlabs.ai, the site of Excession Labs, a security lab, and request a security test.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 71 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using AOPX
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http aopx https://api.aopx.fr/mcp/Capabilities
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.
DiscoveredRead 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.
DiscoveredUse 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.
DiscoveredUse 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 125 ms | 4 |