AOPX MCP server
fr.aopx/aopxaopx.frstreamable-httpv0.1.0Scanned
Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AOPX MCP server can do
The AOPX MCP server is published by aopx.fr, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: recommend_provider and report_outcome), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
recommend_providerUse when a software agent needs an AOPX recommendation for the SEARCH category instead of hard-coding a single supported provider.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
report_outcomeUse only after a real external execution of a provider path returned by recommend_provider.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
Only reads 2Show 2 read-only tools
public_outcomesRead recent caller-reported production outcomes from the AOPX public evidence surface.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
public_statsRead aggregate public statistics from the AOPX production pilot, including consultation and reported-outcome activity.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.aopx.fr/mcp/: tools/list returned 4 tools to an anonymous client, including recommend_provider (write), report_outcome (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http aopx https://api.aopx.fr/mcp/claude mcp add --transport http aopx https://api.aopx.fr/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__aopx__public_stats",
"mcp__aopx__public_outcomes"
],
"ask": [
"mcp__aopx__recommend_provider",
"mcp__aopx__report_outcome"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aopx. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/fr.aopx/aopx/verify?hash=b4ed6a6118b2a157af4150453df40c4e5b13a61759b34bd4ba722f0a15f17d0e" | jq -e '.changed == false'Pinned hash b4ed6a6118b2, from Nov 15, 2026, 09:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/fr.aopx/aopx/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/fr.aopx/aopx)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
AOPX MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AOPX MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AOPX MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AOPX MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AOPX MCP server have?
- 4 tools: 2 write, 2 read. recommend_provider, report_outcome, public_stats and public_outcomes.
Does the AOPX MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AOPX MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AOPX MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.