nko
MCP serverDev toolsfind-missing checks whether a company that holds an LEI (Legal Entity Identifier) has a match in the national registry its jurisdiction expects. Once added, your AI can run this check for any entity you ask about and tell you whether the expected registry match exists or is missing.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding find-missing, ask your AI to check whether a specific entity has the registry match its jurisdiction expects.
Then ask your AI: use nko to find missing
What your AI can do with it
- Check whether an LEI-holding entity has a match in the national registry its jurisdiction expects
- Report when the expected registry match is missing
- Run the check for any entity you specify, based on its jurisdiction
From the project's README
As published by nko-llc-tech/nko in README.md.
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
Tools it offers (2)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
find_missingaward_state
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- find-missing MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
io-github-nko-studio-find-missing- Source
- github.com/nko-llc-tech/nko
- Hosted endpoint
https://api.nkodatalabs.com/mcp