MCP.Market

Esma Firds MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/esma-firds·v0.2.1

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Esma Firds yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Esma Firds tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Esma Firds compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,712 ms
faster than 5% of 30,031 servers

Release history: 5 versions in the registry since 2026-09-25, latest 2026-11-01, typically one every 4 days.

Install Esma Firds in Claude Code, Cursor or VS Code

claude mcp add --transport http esma-firds https://gateway.pipeworx.io/esma-firds/mcp
Add to Cursor

What the publisher says

From the Esma Firds repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/esma-firds

ESMA's EU-wide financial instrument reference register (FIRDS) and its MiFID II investment-firm authorisation register (the Union Register) — resolve an ISIN to its issuer LEI, CFI code and every EU trading venue it lists on; search instruments by issuer; and check whether a firm is authorised to provide investment services in the EU. Keyless, live per-query against ESMA's own public Solr endpoint.

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

  • firds_lookup(isin) — resolve one ISIN to 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.
  • firdssearchbyissuer(issuerlei?, issuer_name?, limit?) — every instrument FIRDS holds for one issuer, by LEI (exact) or name (all words must appear, order-independent).
  • esmacheckfirm_authorisation(name?, lei?, limit?) — look up a firm in ESMA's Union Register of investment firms: authorisation status, competent authority, home member state, entity type.

Auth

Keyless.

Data sources

  • GET https://registers.esma.europa.eu/solr/esmaregistersfirds/select — the FIRDS Solr core: one document per (ISIN, trading venue) pair. Backs firdslookup and firdssearchbyissuer.
  • GET https://registers.esma.europa.eu/solr/esmaregistersupreg/select — the Union Register (MiFID II firm authorisation) Solr core, entitytype:ae documents. Backs esmacheckfirmauthorisation.

Both cores are the same public, keyless Solr instance ESMA runs itself behind the FIRDS/register UI at registers.esma.europa.eu — confirmed live 2026-09-23. This pack calls it per request; it does not ingest ESMA's bulk FIRDS full/delta XML files (see Quirks).

Quirks

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Esma Firds: common questions

Is Esma Firds MCP server safe?
Mostly: it is graded B (77/100). Read the Esma Firds safety report
How do I install Esma Firds?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Esma Firds need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Esma Firds maintained?
The last commit was 39 days ago (2026-09-25). The latest release is v0.2.1.
Is Esma Firds up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Esma Firds compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,712 ms (faster than 5% of 30,031 servers). Full comparison.

More from pipeworx-io →