Gleif MCP Server

Verify any company's legal identity in one question. Look up LEI codes, validate counterparties, and trace corporate ownership structures using the official GLEIF database. Covers 2.8M+ entities across 200+ jurisdictions. The gleif mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

The Legal Entity Identifier (LEI) is a 20-character alphanumeric code that uniquely identifies legal entities participating in financial transactions worldwide. It's mandated by 200+ regulations including MiFID II, EMIR, Dodd-Frank, and DORA.

Its toolset

Everything the assistant can do here goes through one of these:

• Authentication — None required
• Documentation — https://www.gleif.org/en/lei-data/gleif-api
• lei_lookup — Get full details for a specific LEI
• validate_lei — Check format, check digits, and status
• batch_lei_lookup — Look up multiple LEIs at once
• search_entity — Search by company name
• search_by_bic — Find LEI from BIC/SWIFT
• search_by_isin — Find issuer LEI from ISIN
• search_by_country — List entities by country
• autocomplete — Entity name suggestions
• get_relationships — Get corporate/fund relationships
• get_lei_issuer — Get details about an LOU

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Gleif's toolset — Authentication, Documentation, lei_lookup and 11 more — is a fair guide to whether it matches your workflow. It is maintained by olgasafonova; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Gleif.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gleif mcp server does with a few real requests.