# Esma Firds (npm · @pipeworx/mcp-esma-firds)

ESMA FIRDS + MiFID authorisation register — the EU's Financial Instruments Reference Data System…

- Trust score: 83/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-esma-firds/esma-firds-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-esma-firds/esma-firds-mcp)
- npm · `@pipeworx/mcp-esma-firds`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-esma-firds/pipeworx-mcp-esma-firds.md), [page](https://verifymcp.io/servers/pipeworx-io-esma-firds/pipeworx-mcp-esma-firds)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-esma-firds`
- 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-esma-firds).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 644 tokens (~214/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Esma Firds MCP server?

Esma Firds runs locally as an npm package, launched with npx -y @pipeworx/mcp-esma-firds. 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-esma-firds -- npx -y @pipeworx/mcp-esma-firds
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-esma-firds -- npx -y @pipeworx/mcp-esma-firds
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-esma-firds --command npx --arg -y --arg @pipeworx/mcp-esma-firds
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +1)

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

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

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.07 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

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

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

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

First indexed and scored.

## MCP tools (3)

### `firds_lookup` (~187 tokens)

Resolve one ISIN via ESMA's FIRDS (Financial Instruments Reference Data System, EU-wide, all MiFID II instruments) to its full name, short name, CFI code, issuer LEI, notional currency, bond fields (maturity, nominal value, fixed rate) or derivative fields (underlying ISIN, expiry, option type) when applicable, and every EU trading venue (MIC) it trades on with each venue's status and first/termination trading date. issuer_lei is the join key into the gleif pack for issuer legal-entity detail and into openfigi for cross-referencing. Covers shares, bonds, ETFs, structured products and listed derivatives reported under MiFIR across the EU/EEA.

Input parameters:

- `isin` (string, required): 12-character ISIN, e.g. "DE0007164600" (SAP SE ordinary share).

### `firds_search_by_issuer` (~210 tokens)

Search ESMA's FIRDS for every instrument reported for one issuer, by issuer LEI (exact match, preferred) or issuer/instrument name (matches if every word appears anywhere in the name, order-independent). Returns each matching (ISIN, venue) record with name, CFI code and issuer LEI, plus the total number of matching records FIRDS holds (which can run into the hundreds for a large issuer across many venues and instrument types — the result is capped at `limit`).

Input parameters:

- `issuer_lei` (string): 20-character issuer LEI, e.g. "529900D6BF99LW9R2E68" (SAP SE). Exact match.
- `issuer_name` (string): Issuer or instrument name; every word must appear in the name, e.g. "Deutsche Bank". Used only if issuer_lei is not given.
- `limit` (number): Max records to return (default 25, max 100).

### `esma_check_firm_authorisation` (~191 tokens)

Look up a firm in ESMA's Union Register of investment firms (the EU-wide MiFID II authorisation register) by entity name (matches if every word appears anywhere in the name, order-independent) or LEI (exact match). Returns each matching entity's authorisation status (Active/Inactive), competent authority, home member state and entity type (investment firm, credit institution, etc.) — answers 'is this entity authorised to provide investment services in the EU'. Distinct from FIRDS: this is the firm register, not the instrument register.

Input parameters:

- `lei` (string): 20-character LEI, exact match. Used only if name is not given.
- `limit` (number): Max records to return (default 20, max 100).
- `name` (string): Entity name; every word must appear in the name, e.g. "Deutsche Bank".

## Diagnostics

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

## Score history

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

## Common questions

### What is the Esma Firds MCP server?

Esma Firds is an MCP server listed in the public MCP registry as io.github.pipeworx-io/esma-firds. ESMA FIRDS + MiFID authorisation register, the EU's Financial Instruments Reference Data System… This page covers its npm package (@pipeworx/mcp-esma-firds).

### Is the Esma Firds MCP server safe to use?

Esma Firds scores 83 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 Esma Firds MCP server expose?

Esma Firds exposes 3 tools: firds_lookup, firds_search_by_issuer, esma_check_firm_authorisation. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.

### Is the Esma Firds MCP server still maintained?

Esma Firds 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 Esma Firds MCP server under?

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

## Links

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