io.github.NKO-STUDIO/find-missing
REMOTE · API.NKODATALABS.COM
Checks if an LEI-holding entity has a match in the national registry its jurisdiction expects.
Available components
Last scanned (13 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Oct 2026.
Category CRM and Sales
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://api.nkodatalabs.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.nkodatalabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nkodatalabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.nkodatalabs.com/mcp | Unreachable | ||
| http (plaintext) | http://api.nkodatalabs.com/mcp | HTTPS enforced | 308 | https://api.nkodatalabs.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
award_state ~280
Given a real, awarded EU public-procurement notice (TED), resolve the winning company's real commercial-registry status TODAY (active, dissolved, insolvency, etc.) - answers "is the company that won this public contract still alive?". Args: notice_id: the TED publication-number of an AWARD notice (e.g. "15-2026") - must be a can-standard/can-social/can-desw/ can-defence notice with a chosen winner, not the original contract notice (cn-standard). api_key: optional - a free key obtained from POST https://api.nkodatalabs.com/v0/keys. Without one, this call still works within a free anonymous trial (5 calls/day per caller IP) - see the response's "trial" field. Coverage today (published honestly, not hidden): Spain and France resolve live via each country's own commercial registry. UK and Hungary are not resolvable yet - UK needs a free Companies House API key not yet configured on this service, Hungary has no free public registry API at all. Natural-person awardees are excluded, never resolved as a company.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| notice_id | string | yes | – |
No output schema declared.
No examples provided.
find_missing ~187
Query whether an entity with a real LEI has a high-confidence match in the national commercial registry its declared jurisdiction would expect. Args: identifier_type: one of "lei", "company_number", "name". identifier: the LEI, registration number, or legal name to look up. api_key: optional - a free key obtained from POST https://api.nkodatalabs.com/v0/keys. Without one, this call still works within a free anonymous trial (5 calls/day per caller IP) - see the response's "trial" field. jurisdiction: optional ISO-3166 alpha-2 country code (e.g. "GB", "ES", "FR").
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| identifier | string | yes | – |
| identifier_type | string | yes | – |
| jurisdiction | – | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.NKO-STUDIO/find-missing MCP server?
io.github.NKO-STUDIO/find-missing is a hosted endpoint at https://api.nkodatalabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.nkodatalabs.com
claude mcp add --transport http nko-studio-find-missing 'https://api.nkodatalabs.com/mcp'
What is the io.github.NKO-STUDIO/find-missing MCP server?
io.github.NKO-STUDIO/find-missing is an MCP server listed in the public MCP registry as io.github.NKO-STUDIO/find-missing. Checks if an LEI-holding entity has a match in the national registry its jurisdiction expects. This page covers its hosted endpoint (https://api.nkodatalabs.com/mcp).
Is the io.github.NKO-STUDIO/find-missing MCP server safe to use?
io.github.NKO-STUDIO/find-missing scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.NKO-STUDIO/find-missing MCP server expose?
io.github.NKO-STUDIO/find-missing exposes 2 tools: find_missing, award_state. Their descriptions and schemas cost roughly 467 tokens of context every time the server is loaded.
Does the io.github.NKO-STUDIO/find-missing MCP server require authentication?
Its publisher declares no required credentials for io.github.NKO-STUDIO/find-missing. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.NKO-STUDIO/find-missing MCP server still maintained?
io.github.NKO-STUDIO/find-missing has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.