About find-missing
find-missing checks whether an LEI-holding entity appears in the national registry expected for its jurisdiction. It is a public NKO Data Labs product interface for checking entity and registry expectations against GLEIF.
Key features
- 01Checks LEI entities against national registries
- 02Compares GLEIF with registry expectations
Use cases
- 01Check an entity's expected national registry presence
- 02Review matches between GLEIF and national registries
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.nkodatalabs.com/mcpclaude mcp add --transport http nko-studio-find-missing https://api.nkodatalabs.com/mcp{"mcpServers":{"nko-studio-find-missing":{"type":"http","url":"https://api.nkodatalabs.com/mcp"}}}Open in Cursor{"servers":{"nko-studio-find-missing":{"type":"http","url":"https://api.nkodatalabs.com/mcp"}}}Open in VS Code{"mcpServers":{"nko-studio-find-missing":{"type":"http","url":"https://api.nkodatalabs.com/mcp"}}}{"mcpServers":{"nko-studio-find-missing":{"serverUrl":"https://api.nkodatalabs.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEnko
NKO Data Labs — public product interfaces (client, OpenAPI, MCP manifests)
Products in this repo
- find_missing — entity/registry expectation checks (GLEIF vs national registries)
- patent_reality_check — NKO Reality Check #001, US patent legal state vs USPTO Official Gazette
https://nkodatalabs.com/?utm_source=github&utm_medium=readme
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.