# UK Data: Sanctions screening (remote · ukdata.reliness.co.uk)

Screen people, companies and ships against UK, US OFAC, EU and UN sanctions lists, daily

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

## Components

- remote · `ukdata.reliness.co.uk`: 74/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening.md), [page](https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening)

## Channel facts

- Endpoint: `https://ukdata.reliness.co.uk/mcp/sanctions-screening`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.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-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1113 tokens (~139/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the UK Data: Sanctions screening MCP server?

UK Data: Sanctions screening is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/sanctions-screening, 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 uk-co-reliness-sanctions-screening 'https://ukdata.reliness.co.uk/mcp/sanctions-screening'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-reliness-sanctions-screening": {
      "url": "https://ukdata.reliness.co.uk/mcp/sanctions-screening"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-reliness-sanctions-screening": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/sanctions-screening"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-reliness-sanctions-screening]
url = "https://ukdata.reliness.co.uk/mcp/sanctions-screening"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-reliness-sanctions-screening": {
      "type": "remote",
      "url": "https://ukdata.reliness.co.uk/mcp/sanctions-screening",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-reliness-sanctions-screening --url 'https://ukdata.reliness.co.uk/mcp/sanctions-screening' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-reliness-sanctions-screening:
    url: "https://ukdata.reliness.co.uk/mcp/sanctions-screening"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-reliness-sanctions-screening": {
      "Transport": "http",
      "Url": "https://ukdata.reliness.co.uk/mcp/sanctions-screening"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-reliness-sanctions-screening -t streamable-http -u 'https://ukdata.reliness.co.uk/mcp/sanctions-screening'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-reliness-sanctions-screening": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/sanctions-screening"
    }
  }
}
```

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-11-20 (score 74, +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-11-18 (score 73, +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-11-16 (score 72, +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-11-14 (score 71, +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-11-12 (score 70, +1)

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

### 2026-11-10 (score 69, +1)

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

### 2026-11-08 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 67)

First indexed and scored.

## MCP tools (8)

### `sanctions_screen` (~265 tokens)

Screen a person, company or ship by name against the UK Sanctions List (FCDO/OFSI), the US OFAC lists, the UN Security Council list and the EU financial sanctions list in one call. Matching tolerates transliteration and spelling variants; date of birth and country re-rank matches but never hide a name match. Returns the listed record, why it matched and which lists were checked. Covers the UK, US OFAC (SDN and Consolidated), EU and UN lists; does not cover politically exposed persons (PEPs). Use for supplier, customer and payment screening. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional nationality or country (name, ISO code or adjective)
- `dob` (string): string, optional date or year of birth
- `limit` (number|string): number 1-100, default 25
- `lists` (string): comma list of uk, un, eu, ofac (default all)
- `minScore` (number|string): number 50-100, default 80
- `name` (string): string, required (or a 7-digit IMO number for a ship)
- `type` (string): person|entity|ship|any (default any)

### `sanctions_check_person` (~137 tokens)

Check whether a named PERSON is on the UK, US (OFAC), EU or UN sanctions lists. Add date or year of birth and nationality to firm up or rule out a match. For onboarding a customer, vetting a director or shareholder, or approving a payment to an individual. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional nationality
- `dob` (string): string, optional date or year of birth
- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required

### `sanctions_check_company` (~103 tokens)

Check whether a COMPANY or organisation is on the UK, US (OFAC), EU or UN sanctions lists, including trading names and aliases. For supplier and customer due diligence and approving payments to businesses. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional
- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required

### `sanctions_check_ship` (~105 tokens)

Check whether a SHIP or vessel is sanctioned (UK, US OFAC, EU, UN), by vessel name, former name or 7-digit IMO number. For shipping, chartering, freight and maritime insurance checks. (cost: 3 credits)

Input parameters:

- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required (vessel name or IMO number)

### `ofac_check` (~128 tokens)

Search the US Treasury OFAC sanctions lists (SDN and Consolidated non-SDN) for a person, company or ship. For US-dollar payments, US counterparties and any OFAC compliance check. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional
- `dob` (string): string, optional
- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required
- `type` (string): person|entity|ship|any

### `uk_sanctions_check` (~139 tokens)

Search the UK Sanctions List (FCDO, enforced by OFSI) for a person, company or ship, with the UK regime, measures (asset freeze, travel ban) and designation date. For UK firms meeting their UK sanctions obligations. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional
- `dob` (string): string, optional
- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required
- `type` (string): person|entity|ship|any

### `eu_sanctions_check` (~116 tokens)

Search the EU consolidated financial sanctions list for a person or organisation, with the EU programme and listing date. For EU counterparties and EU trade. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional
- `dob` (string): string, optional
- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required
- `type` (string): person|entity|any

### `un_sanctions_check` (~120 tokens)

Search the UN Security Council consolidated sanctions list (ISIL/Al-Qaida, Taliban, DPRK, Iran-related and other regimes) for a person or entity. (cost: 3 credits)

Input parameters:

- `country` (string): string, optional
- `dob` (string): string, optional
- `limit` (number|string): number 1-100
- `minScore` (number|string): number 50-100
- `name` (string): string, required
- `type` (string): person|entity|any

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 69
- 2026-11-10: 69
- 2026-11-09: 68
- 2026-11-08: 68
- 2026-11-07: 67

## Common questions

### What is the UK Data: Sanctions screening MCP server?

UK Data: Sanctions screening is an MCP server listed in the public MCP registry as uk.co.reliness/sanctions-screening. Screen people, companies and ships against UK, US OFAC, EU and UN sanctions lists, daily. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/sanctions-screening).

### Is the UK Data: Sanctions screening MCP server safe to use?

UK Data: Sanctions screening scores 74 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 UK Data: Sanctions screening MCP server expose?

UK Data: Sanctions screening exposes 8 tools: sanctions_screen, sanctions_check_person, sanctions_check_company, sanctions_check_ship, ofac_check, and 3 more. Their descriptions and schemas cost roughly 1,113 tokens of context every time the server is loaded.

### Does the UK Data: Sanctions screening MCP server require authentication?

No. We connected to UK Data: Sanctions screening without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UK Data: Sanctions screening MCP server still maintained?

UK Data: Sanctions screening is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the UK Data: Sanctions screening MCP server?

VerifyMCP ran 13 checks on UK Data: Sanctions screening, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ukdata.reliness.co.uk/mcp/sanctions-screening
- Website: https://ukdata.reliness.co.uk/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-reliness-sanctions-screening/mcp-sanctions-screening
