# Sanctions Check (remote · public-domain-check-production.up.railway.app)

Screen crypto wallets and names against US Treasury OFAC sanctions lists. Pay per call via x402.

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

## Components

- remote · `public-domain-check-production.up.railway.app`: 74/100 (this document), [markdown](https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp.md), [page](https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp)

## Channel facts

- Endpoint: `https://public-domain-check-production.up.railway.app/sanctions/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-21.

- **Endpoint Security**: 74/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 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 243 tokens (~81/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 3 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 Check MCP server?

Sanctions Check is a hosted endpoint at https://public-domain-check-production.up.railway.app/sanctions/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 chomkaevan-sanctions-check 'https://public-domain-check-production.up.railway.app/sanctions/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chomkaevan-sanctions-check": {
      "url": "https://public-domain-check-production.up.railway.app/sanctions/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chomkaevan-sanctions-check": {
      "type": "http",
      "url": "https://public-domain-check-production.up.railway.app/sanctions/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chomkaevan-sanctions-check]
url = "https://public-domain-check-production.up.railway.app/sanctions/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chomkaevan-sanctions-check": {
      "type": "remote",
      "url": "https://public-domain-check-production.up.railway.app/sanctions/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chomkaevan-sanctions-check --url 'https://public-domain-check-production.up.railway.app/sanctions/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chomkaevan-sanctions-check:
    url: "https://public-domain-check-production.up.railway.app/sanctions/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chomkaevan-sanctions-check": {
      "Transport": "http",
      "Url": "https://public-domain-check-production.up.railway.app/sanctions/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chomkaevan-sanctions-check -t streamable-http -u 'https://public-domain-check-production.up.railway.app/sanctions/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chomkaevan-sanctions-check": {
      "type": "http",
      "url": "https://public-domain-check-production.up.railway.app/sanctions/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-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 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-16 (score 72, +1)

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

### 2026-11-15 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 71)

First indexed and scored.

## MCP tools (3)

### `check_wallet_sanctions` (~101 tokens)

Check a crypto wallet against OFAC sanctions

Check whether a crypto wallet address is on the US Treasury OFAC sanctions lists. Call this before paying an unknown counterparty, onboarding a wallet, or accepting funds. Covers Bitcoin, Ethereum/EVM, USDT, USDC, Tron, Litecoin, Monero, Solana and more; refreshed every 12 hours. Costs $0.002 (x402, USDC on Base).

Input parameters:

- `address` (string, required): Wallet address (any chain)

### `screen_sanctions_name` (~110 tokens)

Screen a name against OFAC sanctions lists

Screen a person, company, vessel or aircraft name against the US Treasury OFAC SDN and Consolidated sanctions lists, including aliases. Use before onboarding a customer, paying a supplier or signing a counterparty. Returns no_match, potential_match or strong_potential_match with the best candidate and a one-line reason. Costs $0.003 (x402, USDC on Base).

Input parameters:

- `name` (string, required): Person, company, vessel or aircraft name
- `type` (string)

### `sanctions_list_status` (~32 tokens)

Sanctions list status (free)

Free. Which OFAC lists are loaded, how many entries and wallet addresses, and when they were last refreshed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp#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

## Common questions

### What is the Sanctions Check MCP server?

Sanctions Check is an MCP server listed in the public MCP registry as io.github.chomkaevan/sanctions-check. Screen crypto wallets and names against US Treasury OFAC sanctions lists. Pay per call via x402. This page covers its hosted endpoint (https://public-domain-check-production.up.railway.app/sanctions/mcp).

### Is the Sanctions Check MCP server safe to use?

Sanctions Check 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 Sanctions Check MCP server expose?

Sanctions Check exposes 3 tools: check_wallet_sanctions, screen_sanctions_name, sanctions_list_status. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.

### Does the Sanctions Check MCP server require authentication?

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

### Is the Sanctions Check MCP server still maintained?

Sanctions Check 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 Check MCP server?

VerifyMCP ran 13 checks on Sanctions Check, 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://public-domain-check-production.up.railway.app/sanctions/mcp
- Repository: https://github.com/chomkaevan/public-domain-check-mcp
- Website: https://public-domain-check-production.up.railway.app/sanctions
- Changelog RSS feed: https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp.json
- HTML version of this page: https://verifymcp.io/servers/chomkaevan-sanctions-check/sanctions-mcp
