@pipeworx/gleif

Connect: https://gateway.pipeworx.io/gleif/mcp · Install: one-click buttons

Tools: 7

Global Legal Entity Identifier Foundation MCP — LEI lookup, ISIN/BIC-to-entity mapping, and corporate hierarchy, no auth.

Tools

• search_lei(query, country?, status?, page_size?) — fuzzy entity-name search. If country narrows the result to nothing, the filter is dropped and the response says so via country_filter_dropped — GLEIF filters on the registered legal address, which often is not where the entity operates (no Sberbank-named record has a Russian one; they sit in CY/SK/LU/GB).
• get_lei(lei) — full Level 1 record: legal name, addresses, jurisdiction, legal form, and LEI registration status. Accepts a company name as well as a 20-character LEI; a resolved name is echoed back as resolved_from_name.
• get_lei_relationships(lei) — Level 2 direct parent, ultimate parent, direct children (one hop).
• isin_to_lei(isin) — resolve a security’s ISIN to the legal entity that issued it (LEI + legal name). A valid-but-unmapped ISIN is reported as mapped: false, reason: "isin_unmapped" — the mapping lags new issuance, so unmapped ≠ nonexistent.
• lei_to_isins(lei) — all ISINs issued by an entity (LEI or company name accepted). Returns the full set — one entity issues many securities.
• bic_to_lei(bic) — resolve a SWIFT/BIC (8 or 11 chars) to the bank’s legal entity. 8-char codes are padded to the XXX head-office form (GLEIF’s filter matches 11-char BICs only); a branch BIC with no mapping of its own falls back to the head office and says so.
• lei_hierarchy_tree(lei, depth?) — multi-hop ownership: ancestor chain up to the ultimate parent plus a breadth-first subsidiary tree (depth 1–4, default 2, node budget 150/call).

Data source

https://api.gleif.org/api/v1/ — public JSON:API, no key required. ISIN and BIC joins use GLEIF’s official ISIN-to-LEI and BIC-to-LEI mapping files as served through the same API (filter[isin], filter[bic], /lei-records/{lei}/isins).

Passing an LEI

Every tool that takes an lei argument also takes a company name — the name is resolved against the registry and the match is returned alongside the answer. Pass the name whenever that is what you have.

Never construct an LEI code. A guessed 20-character string that happens to be a real LEI belongs to some other company, and GLEIF returns its record with nothing to indicate the wrong entity was fetched — a request for Wirecard AG once came back as Baader Bank Aktiengesellschaft. Codes are checked against the ISO 17442 (ISO 7064 MOD 97-10) check digits before any request is made, and a code that fails is rejected with a message naming search_lei; that catches roughly 96 of every 97 invented codes, but not one that collides with a live record, which is why the name path exists.

Tools

• search_lei — Search the GLEIF LEI registry by legal entity name. Returns matched entities with their 20-character LEI, jurisdiction, status, and BIC/ISIN cross-references. Use the LEI to resolve canonical identity
• get_lei — Fetch the full Level 1 LEI record for a legal entity. Returns legal name, registered address, headquarters address, entity category, legal form, registration authority, LEI registration status (ISSUED
• get_lei_relationships — Fetch Level 2 corporate hierarchy for an LEI: direct parent, ultimate parent, and direct children. Use to map ownership trees across multinational groups. Accepts a company NAME as well as an LEI.
• isin_to_lei — Resolve an ISIN (12-character international securities identifier, e.g. “CH0038863350” or “DE0007164600”) to the LEGAL ENTITY that issued the security: its LEI, registered legal name, jurisdiction, an
• lei_to_isins — List ALL ISINs (securities) issued by a legal entity, from the official GLEIF ISIN-to-LEI mapping. Accepts a 20-character LEI or a company NAME (resolved automatically and echoed back). Answers “what
• bic_to_lei — Resolve a SWIFT/BIC bank identifier code (8 or 11 characters, e.g. “DEUTDEFF” or “DEUTDEFFXXX”) to the bank’s legal entity: LEI, registered legal name, jurisdiction, and status, via the official GLEIF
• lei_hierarchy_tree — Walk the FULL corporate ownership hierarchy for an entity in one call: the ancestor chain from the entity up to its ultimate parent, plus a multi-level tree of subsidiaries below it (breadth-first ove