# 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.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `api.nkodatalabs.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/nko-studio-find-missing/api.md), [page](https://verifymcp.io/servers/nko-studio-find-missing/api)

## Channel facts

- Endpoint: `https://api.nkodatalabs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 738 tokens (~369/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http nko-studio-find-missing 'https://api.nkodatalabs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nko-studio-find-missing": {
      "url": "https://api.nkodatalabs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nko-studio-find-missing": {
      "type": "http",
      "url": "https://api.nkodatalabs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nko-studio-find-missing]
url = "https://api.nkodatalabs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nko-studio-find-missing": {
      "type": "remote",
      "url": "https://api.nkodatalabs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nko-studio-find-missing --url 'https://api.nkodatalabs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nko-studio-find-missing:
    url: "https://api.nkodatalabs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nko-studio-find-missing": {
      "Transport": "http",
      "Url": "https://api.nkodatalabs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nko-studio-find-missing -t streamable-http -u 'https://api.nkodatalabs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nko-studio-find-missing": {
      "type": "http",
      "url": "https://api.nkodatalabs.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 61, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_missing” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 382 → 738
- [functional] New tool “award_state”
- [cosmetic] “find_missing” made “api_key” optional

## MCP tools (2)

### `find_missing` (~187 tokens)

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").

Input parameters:

- `api_key`
- `identifier` (string, required)
- `identifier_type` (string, required)
- `jurisdiction`

### `award_state` (~280 tokens)

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.

Input parameters:

- `api_key`
- `notice_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nko-studio-find-missing/api#diagnostics

## Score history

- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 67
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65
- 2026-09-14: 65
- 2026-09-13: 64
- 2026-09-12: 64
- 2026-09-11: 63
- 2026-09-10: 63
- 2026-09-09: 62
- 2026-09-08: 62
- 2026-09-07: 61
- 2026-09-06: 61
- 2026-09-05: 60
- 2026-09-04: 62
- 2026-09-03: 62
- 2026-09-02: 61
- 2026-09-01: 61

## Common questions

### 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 68 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?

No. We connected to io.github.NKO-STUDIO/find-missing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.NKO-STUDIO/find-missing MCP server still maintained?

io.github.NKO-STUDIO/find-missing is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.nkodatalabs.com/mcp
- Repository: https://github.com/NKO-LLC-TECH/nko
- Website: https://nkodatalabs.com/products/find-missing/
- Changelog RSS feed: https://verifymcp.io/servers/nko-studio-find-missing/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/nko-studio-find-missing/api.json
- HTML version of this page: https://verifymcp.io/servers/nko-studio-find-missing/api