Gleif logo

Gleif

Look up LEIs, map ISINs and BICs to legal entities, and inspect ownership groups through GLEIF data without authentication.

Install Gleif

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gleif": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-gleif"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 11 tools correctly ().

Overview

Gleif MCP server connects AI agents to GLEIF’s public API for LEI searches, entity records, ownership relationships, ISIN and BIC mappings, and bulk screening. It accepts company names as well as identifiers, decodes legal-form and registration-authority codes, and can return consolidated group membership across jurisdictions. Use it for financial-entity due diligence, issuer identification, corporate-structure research, or jurisdiction-based LEI screening without an API key. The hosted MCP endpoint also exposes shared Pipeworx gateway tools alongside the Gleif-specific tools.

Use cases

  • Search for a legal entity by company name or LEI
  • Map an ISIN or BIC to its issuing legal entity
  • Trace parent, subsidiary, and consolidated-group relationships
  • Screen LEIs by jurisdiction, status, or recent event
  • Decode legal-form and registration-authority codes

Key features

  • Unauthenticated access to GLEIF data
  • LEI, ISIN, and BIC entity resolution
  • Corporate hierarchy and group-membership queries
  • Bulk LEI screening with date and event filters
  • ISO 20275 and registration-authority decoding
  • Company-name input for identifier-based tools

Tools11

What Gleif lets your agent do. Expand a tool for its parameters.

Verified live~3.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

12/12 checks healthy over the last 62d

What it can do

From the 11 tools this server returned when we ran it; 11 declare their own safety hints.

Handles credentials · 1Makes network requests · 11Read-only tools · 11
Network at startup4 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age174 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @pipeworx/mcp-gleif (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.5kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed11Callable tools this server registers over MCP.

How Gleif works

What Gleif does

Gleif MCP server gives MCP clients access to data from the Global Legal Entity Identifier Foundation (GLEIF). Its core use is resolving and inspecting Legal Entity Identifiers (LEIs), including legal names, registered addresses, jurisdictions, legal forms, registration status, and national registration details.

The server also connects securities and banking identifiers to legal entities. ISIN lookups identify the issuing entity, while BIC lookups resolve an eight- or eleven-character SWIFT/BIC to a bank’s legal entity. Reverse lookup is available too: given an LEI or company name, the server returns the ISINs issued by that entity.

Ownership queries cover direct parents, ultimate parents, direct children, multi-level hierarchy trees, and complete consolidated groups. Bulk screening can filter GLEIF’s LEI population by jurisdiction, registration or entity status, category, event type, name, and date window.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/gleif/mcp, with no authentication required. The underlying entity and relationship queries use GLEIF’s public JSON:API. ISIN and BIC joins use GLEIF’s official mapping data served through that API.

Group-membership and bulk-screening responses use GLEIF’s golden copy of Level 1 entity reference data and Level 2 relationship records. These datasets are refreshed daily, while GLEIF publishes the golden copy three times a day. Responses include data_as_of, identifying the GLEIF publication time represented by the result.

Identifier arguments can be LEIs or company names. Name resolution is returned with the result. LEI inputs are checked against ISO 17442 check digits before requests are made, but a valid-looking identifier can still belong to a different entity, so searching by name is preferable when the LEI is uncertain.

Setup and configuration

Add the hosted endpoint to an MCP client such as Claude Desktop, Cursor, or Windsurf:

config.json
{
  "mcpServers": {
    "gleif": {
      "url": "https://gateway.pipeworx.io/gleif/mcp"
    }
  }
}

A full Pipeworx gateway endpoint is also available at https://gateway.pipeworx.io/mcp. Both endpoints reach the same gateway and data sources. The scoped endpoint lists Gleif tools directly but also includes shared Pipeworx tools such as discovery, routing, and memory functions.

Tools and capabilities

  • Search LEIs by entity name, with optional country, status, and page-size filters.
  • Retrieve full Level 1 LEI records and decode legal-form and registration-authority codes.
  • Resolve ISINs to issuers and list all ISINs associated with an entity.
  • Resolve eight- or eleven-character BICs, including head-office fallback for unmapped branches.
  • Retrieve direct relationships, hierarchy trees, and complete consolidated groups.
  • Screen the broader LEI population by jurisdiction, status, event, date, category, or name.
  • Decode ISO 20275 legal-form codes and GLEIF registration-authority codes.

Limitations and notes

An ISIN that has no mapping is reported as unmapped; that result does not prove the security is nonexistent. Eight-character BICs are normalized to the eleven-character head-office form, and branch lookups can fall back to the head office.

Group results exclude fund-management links because those links do not represent ownership. Group member lists have a default limit of 300 and a maximum of 2,000 entries; the response indicates when the list is capped. Hierarchy trees support depths from one through four, defaulting to two, with a 150-node call budget.

Bulk screening treats merger records as retired entities accompanied by a merger or absorption event and successor LEI. Sole-proprietor names are withheld from bulk results. GLEIF data is provided under the CC0 licence through its Access Service; the integration itself is described as unofficial and independent of GLEIF.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Gleif

Gleif is an MCP server that connects AI clients to GLEIF’s public API and golden-copy datasets. Its main tools search and retrieve LEI records, map ISINs and BICs to legal entities, inspect ownership hierarchies and consolidated groups, screen LEIs in bulk, and decode legal-form and registration-authority codes without authentication.

Add the hosted URL `https://gateway.pipeworx.io/gleif/mcp` to your MCP client configuration. The documented setup uses a `gleif` server entry with that URL and works with clients including Claude Desktop, Cursor, and Windsurf; no API key is required.

Yes, Gleif maps ISINs to the legal entity that issued them and resolves eight- or eleven-character BICs to bank entities. An unmapped but valid ISIN is returned as `mapped: false`; a branch BIC can fall back to its head office when no separate mapping exists.

Yes, Gleif returns direct parents, ultimate parents, direct children, multi-hop hierarchy trees, and consolidated group members. Group queries can start with an LEI or company name and include member counts, jurisdiction counts, and the GLEIF publication timestamp.

Yes, Cursor is named as a supported MCP client in the setup example. Configure Cursor with the hosted `https://gateway.pipeworx.io/gleif/mcp` endpoint; authentication is not required.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGleif AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gleif?style=directory)](https://allmcps.com/mcp/gleif)
HTML Embed
<a href="https://allmcps.com/mcp/gleif"><img src="https://allmcps.com/api/badge/gleif?style=directory" alt="Gleif on AllMCPs" /></a>