Get the FREE Ultimate OpenClaw Setup Guide →

gleif

MCP server for GLEIF LEI (Legal Entity Identifier) database access

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio olgasafonova-gleif-mcp-server gleif-mcp-server

How to use

GLEIF MCP Server provides a suite of tools to verify and enrich company identity data by leveraging the official GLEIF database. It exposes capabilities such as LEI lookups, batch LEI processing, entity search by name, cross-referencing BIC/SWIFT and ISIN to related LEIs, and insights into corporate ownership structures. The server is designed to integrate with MCP-compatible tools like Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and similar environments, enabling natural language commands (e.g., Look up Apple’s LEI using GLEIF) to trigger data retrieval and presentation from the GLEIF backend. Core features include fast LEI lookups, batch processing (up to 100 LEIs), entity search with fuzzy matching and pagination, LEI validation, and support for related identifiers (BIC/SWIFT, ISIN) and jurisdictional listings. It emphasizes offline-friendly performance with local caching and built-in retry and rate-limiting behavior for reliability.

To use the server within your MCP-enabled workflow, add the gleif server to your tool’s configuration with the path to the gleif-mcp-server binary. Then issue supported MCP commands via your client: use lei_lookup to fetch full details for a LEI, batch_lei_lookup for multiple LEIs, search_entity for company name queries, search_by_bic or search_by_isin to map identifiers to LEIs, and explore ownership and compliance tools for corporate structures. The server requires no external API key and relies on the public GLEIF data sources, making it straightforward to integrate into onboarding, compliance checks, due diligence, and data enrichment pipelines.

How to install

Prerequisites:

  • Go 1.25+ for building from source or installing from source
  • A supported OS (macOS, Linux, Windows) for binary usage
  1. Download the pre-built binary
  • Visit the releases page to obtain the appropriate binary for your platform, e.g. gleif-mcp-server-darwin-arm64, gleif-mcp-server-linux-amd64, or gleif-mcp-server-windows-amd64.exe
  • Make the binary executable where needed (example for macOS/Linux):
chmod +x gleif-mcp-server-darwin-arm64
  1. Build from source
  • Ensure Go 1.25+ is installed
  • Clone the repository and build:
git clone https://github.com/olgasafonova/gleif-mcp-server.git
cd gleif-mcp-server
go build -o gleif-mcp-server .
  1. Install via Go
  • Install the latest release into your Go bin:
go install github.com/olgasafonova/gleif-mcp-server@latest
  1. Verify installation
  • Run the server binary to ensure it starts and listens for MCP clients. Example (adjust path as needed):
./gleif-mcp-server --help
  1. Integration with MCP clients
  • After obtaining the binary, configure your MCP client (Claude, Cursor, etc.) to point to the gleif-mcp-server executable as shown in the Tools Setup section of the README.

Additional notes

Tips and notes:

  • The server is designed to operate without an API key, relying on GLEIF’s public data. Ensure you respect the standard rate limits and implement retries where appropriate.
  • The MCP toolset includes functions like lei_lookup, validate_lei, batch_lei_lookup, search_entity, search_by_bic, search_by_isin, and country-based browsing. Use the batch endpoint for high-volume requests with a cap (e.g., up to 100 LEIs per batch).
  • If you encounter startup issues, verify that the binary has execute permissions and that the path provided to clients is correct. On macOS, you may also need to bypass quarantine attributes for downloaded binaries.
  • When integrating with Claude or other clients, you can name the server gleif and reference the binary path in your mcp.json (Claude Desktop, Cursor, VS Code, Windsurf, etc.).
  • Logs and error messages are useful for diagnosing LEI format validation errors, missing LEIs in the dataset, or connectivity problems with the GLEIF data sources.

Related MCP Servers

Sponsor this space

Reach thousands of developers