# Sanctions Screen (OFAC, UN, EU, UK) (remote · sanctions-screen.agent-data-apis.workers.dev)

Fuzzy sanctions screening for people, companies, vessels: OFAC, UN, EU, UK. Pay per call via x402.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `sanctions-screen.agent-data-apis.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen.md), [page](https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen)

## Channel facts

- Endpoint: `https://sanctions-screen.agent-data-apis.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 265 tokens (~88/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Sanctions Screen (OFAC, UN, EU, UK) MCP server?

Sanctions Screen (OFAC, UN, EU, UK) is a hosted endpoint at https://sanctions-screen.agent-data-apis.workers.dev/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 dagu3371-sanctions-screen 'https://sanctions-screen.agent-data-apis.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dagu3371-sanctions-screen": {
      "url": "https://sanctions-screen.agent-data-apis.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dagu3371-sanctions-screen": {
      "type": "http",
      "url": "https://sanctions-screen.agent-data-apis.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dagu3371-sanctions-screen]
url = "https://sanctions-screen.agent-data-apis.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dagu3371-sanctions-screen": {
      "type": "remote",
      "url": "https://sanctions-screen.agent-data-apis.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dagu3371-sanctions-screen --url 'https://sanctions-screen.agent-data-apis.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dagu3371-sanctions-screen:
    url: "https://sanctions-screen.agent-data-apis.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dagu3371-sanctions-screen": {
      "Transport": "http",
      "Url": "https://sanctions-screen.agent-data-apis.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dagu3371-sanctions-screen -t streamable-http -u 'https://sanctions-screen.agent-data-apis.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dagu3371-sanctions-screen": {
      "type": "http",
      "url": "https://sanctions-screen.agent-data-apis.workers.dev/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-11-21 (score 65, +1)

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

### 2026-11-19 (score 64, +1)

- [security] Tool “screen_sanctions” rewrote its description, which is the text the model reads

### 2026-11-18 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 63)

First indexed and scored.

## MCP tools (3)

### `screen_sanctions` (~105 tokens)

Sanctions screening (OFAC, UN, EU, UK)

Fuzzy-match one name against US OFAC (SDN + Consolidated), UN, EU and UK sanctions lists. Returns scored candidate matches with programs, countries, DOB and list references. $0.005 per call after the free daily quota.

Input parameters:

- `lists` (array)
- `min_score` (number): Match threshold, default 0.85
- `name` (string, required): Person, company, vessel or aircraft name
- `type` (string)

### `screen_sanctions_batch` (~73 tokens)

Batch sanctions screening

Screen up to 10 names in one call against OFAC, UN, EU and UK sanctions lists. $0.05 per call after the free daily quota.

Input parameters:

- `lists` (array)
- `min_score` (number)
- `names` (array, required)
- `type` (string)

### `sanctions_lists_status` (~25 tokens)

Sanctions list freshness (free)

Free. When the sanctions lists were last refreshed and how many entries each contains.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63

## Common questions

### What is the Sanctions Screen (OFAC, UN, EU, UK) MCP server?

Sanctions Screen (OFAC, UN, EU, UK) is an MCP server listed in the public MCP registry as io.github.dagu3371/sanctions-screen. Fuzzy sanctions screening for people, companies, vessels: OFAC, UN, EU, UK. Pay per call via x402. This page covers its hosted endpoint (https://sanctions-screen.agent-data-apis.workers.dev/mcp).

### Is the Sanctions Screen (OFAC, UN, EU, UK) MCP server safe to use?

Sanctions Screen (OFAC, UN, EU, UK) scores 65 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 Sanctions Screen (OFAC, UN, EU, UK) MCP server expose?

Sanctions Screen (OFAC, UN, EU, UK) exposes 3 tools: screen_sanctions, screen_sanctions_batch, sanctions_lists_status. Their descriptions and schemas cost roughly 203 tokens of context every time the server is loaded.

### Does the Sanctions Screen (OFAC, UN, EU, UK) MCP server require authentication?

No. We connected to Sanctions Screen (OFAC, UN, EU, UK) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sanctions Screen (OFAC, UN, EU, UK) MCP server still maintained?

Sanctions Screen (OFAC, UN, EU, UK) 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 Sanctions Screen (OFAC, UN, EU, UK) MCP server?

VerifyMCP ran 12 checks on Sanctions Screen (OFAC, UN, EU, UK), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Sanctions Screen (OFAC, UN, EU, UK): HTTPS. 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://sanctions-screen.agent-data-apis.workers.dev/mcp
- Website: https://sanctions-screen.agent-data-apis.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen.xml
- Changelog JSON feed: https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen.json
- HTML version of this page: https://verifymcp.io/servers/dagu3371-sanctions-screen/sanctions-screen
