GLEIF MCP Server is an MCP (Model Context Protocol)-based server for accessing the GLEIF (Global Legal Entity Identifier Foundation) LEI (Legal Entity Identifier) database. An LEI is a 20-character alphanumeric code used to uniquely identify legal entities participating in global financial transactions, and is required by more than 200 regulations including MiFID II, EMIR, Dodd-Frank, and DORA. The database covers more than 2.8 million entities across more than 200 jurisdictions.
Purpose: This server is mainly used to verify a company's legal identity, look up LEI codes, verify counterparties, and trace corporate ownership structures through natural-language question-and-answer. Typical uses include KYC and account opening (verifying counterparty identity before contracting), compliance checks (verifying LEIs for MiFID II, EMIR, or DORA reporting), due diligence (researching corporate ownership chains and ultimate parent companies), financial analysis (cross-referencing securities ISINs and bank BIC/SWIFT codes with legal entities), and data enrichment (batch-processing company lists and adding LEI data).
Main capabilities: Provides 12 tools, covering categories such as core queries, financial identifiers, relationships and compliance, and LEI issuing organizations. Core queries include: retrieving full entity details by LEI code, batch queries (up to 100 at a time), fuzzy company search by name (with pagination), and validating LEI format and check digits (ISO 17442) and registration status. Financial identifiers include: finding a bank LEI from a BIC code, finding a securities issuer LEI from an ISIN code, and listing entities by jurisdiction. Relationships and compliance include: querying parent companies, subsidiaries, ultimate parent companies, fund managers, umbrella funds, sub-funds, Level 2 data exceptions and reasons, and listing all local operating units (LOUs) and their details.
How to use: You can download precompiled binaries for each platform from the releases page, or build from source (requires Go 1.25+). Configure the binary path in an MCP-compatible client, such as Claude Desktop's claude_desktop_config.json, Claude Code, Cursor's .cursor/mcp.json, VS Code's Continue extension .continue/config.json, Windsurf's ~/.codeium/windsurf/mcp_config.json, Cline's MCP settings or .vscode/cline_mcp_settings.json, and Antigravity's ~/.antigravity/mcp.json. After configuration, restart the client, and you can ask questions in natural language, such as "Find LEI HWUPKR0MPOU8FGXBT394" or "Find the LEI corresponding to BIC DEUTDEFF".
Technical details: This server wraps the GLEIF public API (base URL:https://api.gleif.org/api/v1),无需认证,速率限制为每分钟 60 requests. Results are cached locally, so repeated queries can return instantly; timeouts, retries, and rate limiting are handled automatically to prevent exceeding the GLEIF quota. All tools return JSON, including relevant fields and pagination information, and errors are returned in a structured form.
Limitations: The GLEIF database is updated daily, so newly issued LEIs may not appear immediately; the first request may be slower due to cache warming; the GLEIF API occasionally has latency spikes, which are handled by automatic retries. If a "rate limit exceeded" error occurs, the server retries automatically; if it persists, you need to reduce concurrent requests or wait a few minutes. macOS will block downloaded files, so you need to run chmod +x gleif-mcp-server in the terminal and configure an absolute path. This tool is released under the MIT license.