fr-amf-sanctions
by pipeworx-io
README.md
# @pipeworx/fr-amf-sanctions
Autorité des marchés financiers (AMF, France): decisions of the Commission des sanctions and accords de composition administrative (settlements) against firms: asset managers, investment services firms, banks and listed issuers, with the themes sanctioned. French text is kept as published.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2006+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `amf_sanctions_search(query?, kind?, year?, limit?)` -- searches the AMF's list of decisions and settlements, newest first. The keyword matches the firm name, the reference and the themes. `kind` is `decision` (Commission des sanctions) or `transaction` (accord de composition). Each hit: id, reference (SAN-2026-07, TRA-2025-18), publication date, decision date, firm names as the AMF writes them, themes, link. `individuals_dropped` and `items_without_a_firm` count what was not returned.
- `amf_sanction_get(id)` -- one case by its id (such as `decisions-de-la-commission-des-sanctions/san-2025-12`): the same fields plus the link to the decision document (PDF), which carries the reasoning and the amount. An unknown id is `found:false`.
Every response carries `source` and `data_as_of` (the newest publication date).
## Auth
Keyless.
## Data sources
- Autorité des marchés financiers, decisions of the Commission des sanctions and approved settlements. Read live per call, nothing stored. The list covers about 200 publications back to late 2018.
Privacy: firms only. AMF titles name the firm and the individuals together ("la société X et de MM. A et B"). The title is cut at the first honorific (M., MM., Mme) and everything after it is removed and counted in `individuals_dropped`; titles naming individuals alone are dropped and counted in `items_without_a_firm`. The decision document linked from a case may name individuals; the pack does not.
Traps worth knowing: a zero-match search means no match in the published list, not that a firm has a clean record; the publication date is when the AMF posted the case, `decision_date` is the date in its title; an individual named without an honorific would not be recognised as one.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"fr-amf-sanctions": {
"url": "https://gateway.pipeworx.io/fr-amf-sanctions/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/fr-amf-sanctions/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 2006+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.
## No MCP client? Call it over HTTP
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/amf_sanctions_search \
-H 'Content-Type: application/json' \
-d '{"query":"Caceis"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/amf_sanctions_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-fr-amf-sanctions` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/fr-amf-sanctions/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"fr-amf-sanctions": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-fr-amf-sanctions"]
}
}
}
```
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.
## Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:
```
ask_pipeworx({ question: "your question about Fr Amf Sanctions data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues