Esma Firds
NPM · @PIPEWORX/MCP-ESMA-FIRDS · 2 COMPONENTS
ESMA FIRDS + MiFID authorisation register — the EU's Financial Instruments Reference Data System…
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-esma-firds). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +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.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-esma-firds@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-esma-firds |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-esma-firds/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635927018 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:45b0b2b72e5408e3cd9d47b5b75ada83262d95994ec79579de8d039184fb54d62ffa04fc1c83c5c4a912ebcca160655900d3d79df259a091c376d2a4e |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
esma_check_firm_authorisation ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
firds_lookup ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| isin | string | yes | 12-character ISIN, e.g. "DE0007164600" (SAP SE ordinary share). |
No output schema declared.
No examples provided.
firds_search_by_issuer ~210
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-esma-firds
claude mcp add pipeworx-io-esma-firds -- npx -y @pipeworx/mcp-esma-firds
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.