# Amf Filings (npm · @pipeworx/mcp-amf-filings)

France AMF Regulated Filings MCP — keyless, same-day-fresh.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-amf-filings/amf-filings-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-amf-filings/amf-filings-mcp)
- npm · `@pipeworx/mcp-amf-filings`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings.md), [page](https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-amf-filings`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-amf-filings).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1019 tokens (~509/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Amf Filings MCP server?

Amf Filings runs locally as an npm package, launched with npx -y @pipeworx/mcp-amf-filings. 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 pipeworx-io-amf-filings -- npx -y @pipeworx/mcp-amf-filings
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-amf-filings": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-amf-filings"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-amf-filings": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-amf-filings"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-amf-filings -- npx -y @pipeworx/mcp-amf-filings
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-amf-filings": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-amf-filings"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-amf-filings --command npx --arg -y --arg @pipeworx/mcp-amf-filings
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-amf-filings:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-amf-filings"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-amf-filings": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-amf-filings"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-amf-filings -t stdio -c npx -a -y @pipeworx/mcp-amf-filings
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-amf-filings": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-amf-filings"
      ]
    }
  }
}
```

## 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-11-05 (score 81, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-03 (score 80, +1)

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

### 2026-11-01 (score 79, +1)

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

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

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (2)

### `amf_search_filings` (~852 tokens)

Search French AMF-regulated company disclosures (résultats, franchissements de seuils, information privilégiée, rachats d'actions, and similar) from Info-financière, the French Officially Appointed Mechanism. PREFER OVER esef_filing_search FOR FRENCH ISSUERS — this source is updated same-day, unlike the community ESEF index which runs months behind for French/EU filings. Identify the issuer with isin (most reliable), lei (frequently null — do not rely on it alone), or a free-text company name; narrow by date_from/date_to (ISO date, UTC) — date_to IS INCLUSIVE of that whole UTC day, so a single-day check sets date_from and date_to to the SAME date (e.g. both "2026-10-16" to get everything published that day); a date_from after date_to returns empty_reason:"empty_window" rather than a bare zero. ALL THREE ARE OPTIONAL — omit company/isin/lei entirely to get every issuer's filings in the date window in ONE call (paginate with limit/offset only if a single day's market-wide volume exceeds the 100-row limit); this is far cheaper than calling once per issuer for a multi-issuer daily check. company is matched against the AMF's own LEGAL-NAME field (e.g. "TELEVISION FRANCAISE 1", not "TF1") — a trade-name search that matches zero legal-name rows automatically retries against disclosure titles and the response says matched_via:"title" when that is what found it, so prefer isin when you have it. Bilingual issuers publish each release TWICE (fr + en, separate ids, same minute) — pass language to get one edition, or group results by the returned language_pair_key. subtype_of_information is normalised to a real null (some disseminators send the literal string "NULL"). Returns disclosure EVENTS — title, issuer, timestamp, and a PDF/document link — NOT extracted XBRL facts.

Input parameters:

- `company` (string): Free-text issuer name search, e.g. "TotalEnergies", "LVMH". Matches on the AMF's own LEGAL-NAME company field first; a distinct legal entity (e.g. a listed subsidiary) with a similar name may also ma…
- `date_from` (string): Only filings published on or after this date (YYYY-MM-DD, UTC). Filters on the actual AMF publication timestamp.
- `date_to` (string): Only filings published on or before this date (YYYY-MM-DD, UTC, INCLUSIVE — the last day you want included). For a single-day check pass the same date as date_from. The upstream API's own bound is ex…
- `isin` (string): Issuer ISIN, e.g. "FR0013230950". The most reliable identifier in this dataset — prefer this over lei or company name when known.
- `language` (string): Filter to one language edition when an issuer files bilingual pairs: "fr" or "en". Omit to get both (each language edition is a separate row with its own id).
- `lei` (string): Issuer LEI (Legal Entity Identifier), e.g. "9695002GVC14VHLFIH85". Populated on many but not all rows — a miss does not mean the issuer has no filings; retry with isin or company.
- `limit` (number|string): Number of filings to return (1-100, clamped if you pass more — the response reports limit_clamped_from when it does). Default 10.
- `offset` (number|string): Result offset for pagination. Default 0.

### `amf_get_filing` (~111 tokens)

Fetch a single French AMF-regulated disclosure by its Info-financière record id (uin_idt_uin, e.g. "008731_20260923") from amf_search_filings results. Returns the full shaped record — title, issuer, ISIN/LEI, publication timestamp, and the document (PDF) URL.

Input parameters:

- `id` (string, required): Info-financière record id (uin_idt_uin), e.g. "008731_20260923".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77

## Common questions

### What is the Amf Filings MCP server?

Amf Filings is an MCP server listed in the public MCP registry as io.github.pipeworx-io/amf-filings. France AMF Regulated Filings MCP, keyless, same-day-fresh. This page covers its npm package (@pipeworx/mcp-amf-filings).

### Is the Amf Filings MCP server safe to use?

Amf Filings scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Amf Filings MCP server expose?

Amf Filings exposes 2 tools: amf_search_filings, amf_get_filing. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.

### Is the Amf Filings MCP server still maintained?

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

### What licence is the Amf Filings MCP server under?

Amf Filings declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Amf Filings MCP server?

VerifyMCP ran 15 checks on Amf Filings, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Amf Filings: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-amf-filings
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-amf-filings
- Repository: https://github.com/pipeworx-io/mcp-amf-filings
- Website: https://pipeworx.io/packs/amf-filings
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-amf-filings/pipeworx-mcp-amf-filings