# P0: sanctions, KYB and payee checks (remote · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev)

Sanctions screening, LEI lookup and payee checks for AI agents, pay per call over x402 or MPP

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

## Components

- remote · `x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance.md), [page](https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance)

## Channel facts

- Endpoint: `https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2421 tokens (~220/item across 11 items; 11 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the P0: sanctions, KYB and payee checks MCP server?

P0: sanctions, KYB and payee checks is a hosted endpoint at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance, 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 dev-workers-x402-bazaar-rank-worker-x402-bazaar- 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "type": "http",
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-x402-bazaar-rank-worker-x402-bazaar-]
url = "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "type": "remote",
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-x402-bazaar-rank-worker-x402-bazaar- --url 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-x402-bazaar-rank-worker-x402-bazaar-:
    url: "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "Transport": "http",
      "Url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-x402-bazaar-rank-worker-x402-bazaar- -t streamable-http -u 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-x402-bazaar-rank-worker-x402-bazaar-": {
      "type": "http",
      "url": "https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance"
    }
  }
}
```

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 70, +1)

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

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

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

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

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

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

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

### 2026-11-15 (score 67, +1)

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

### 2026-11-13 (score 66, +1)

- [security] Tool “bank_us” rewrote its description, which is the text the model reads
- [security] Tool “check_counterparty” rewrote its description, which is the text the model reads
- [security] Tool “check_payee” rewrote its description, which is the text the model reads
- [security] Tool “company_lei” rewrote its description, which is the text the model reads
- [security] Tool “company_lei_batch” rewrote its description, which is the text the model reads
- [security] Tool “lei_changes” rewrote its description, which is the text the model reads
- [security] Tool “sanctions_changes” rewrote its description, which is the text the model reads
- [security] Tool “sanctions_screening” rewrote its description, which is the text the model reads
- [security] Tool “sanctions_screening_batch” rewrote its description, which is the text the model reads
- [security] Tool “token_risk” rewrote its description, which is the text the model reads
- [security] Tool “wallet_risk” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 282 → 221
- [functional] Schema quality: good → excellent

### 2026-11-12 (score 65, +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 64, +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.

## MCP tools (11)

### `sanctions_screening` (~299 tokens)

Sanctions screening

Use when you need to screen a wallet address or a person/company name against sanctions lists before paying or trading: OFAC SDN, UK, EU, Canada and US CSL in one call (UK and Canada: organisations and wallets only). Returns the paid x402 request for your input (GET /sanctions/check, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Sanctions lists only (OFAC SDN, UK, EU, Canada, US CSL; UK and Canada: organisations and wallets only). Send address or name, not both. For a broader rule-based risk label use wallet_risk (addresses) or token_risk (tokens); for a list of addresses use sanctions_screening_batch; for a payee address before paying use check_payee; for a company or person with country or LEI use check_counterparty. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `address` (string): crypto address to screen (send this or name)
- `limit` (integer): name matches only: max hits
- `min_score` (number): name matches only: lowest similarity score to report
- `name` (string): person or entity name in Latin letters (transliterated), at least one word of 3+ characters (send this or address)

### `sanctions_screening_batch` (~152 tokens)

Sanctions screening batch

Use when you need to screen a list of wallet addresses against sanctions lists in one call: up to 25 per POST (0x, BTC, TRX, SOL and any other 20-128 character address). Returns the paid x402 request for your input (POST /sanctions/check/batch, $0.125 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one address or a name use sanctions_screening.

Input parameters:

- `addresses` (array, required): 1 to 25 crypto addresses to screen (as written on their chains); duplicates are removed; names are not accepted

### `sanctions_changes` (~206 tokens)

Sanctions changes

Use when you run sanctions monitoring and need what changed since your last run: entries added, removed and amended on OFAC SDN, UK, EU, Canada and US CSL since a date, one format, with list. Returns the paid x402 request for your input (GET /sanctions/changes, $0.02 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `limit` (integer): Events per page, default 100
- `lists` (string): Optional comma list of ofac, uk, eu, ca, csl; default all
- `offset` (integer): Events to skip (newest first), default 0
- `since` (string, required): Date YYYY-MM-DD: changes in list versions dated on or after it (log keeps 90 days)

### `check_counterparty` (~243 tokens)

Check counterparty

Use when you need to vet a counterparty before paying or onboarding it: one call screens a name (and an optional wallet address) against OFAC SDN, UK, EU, Canada and US CSL. Returns the paid x402 request for your input (GET /check/counterparty, $0.015 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Sanctions part: UK and Canada: organisations and wallets only. A name, optionally with country, LEI or wallet address; for one payee address before paying use check_payee; for a plain list lookup of an address or name use sanctions_screening. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `address` (string): Optional crypto wallet address to screen too
- `country` (string): Optional ISO country, e.g. DE (non-US skips the FDIC section)
- `lei` (string): Optional 20-character LEI: read instead of a name search
- `name` (string, required): Counterparty name in Latin letters

### `check_payee` (~218 tokens)

Check payee

Use before an agent pays an address: one call screens the payee address against OFAC SDN, UK and EU wallet entries (sanctions lists), adds the rule-based wallet risk (EVM). Returns the paid x402 request for your input (GET /check/payee, $0.015 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. One payee address (0x EVM or Solana): sanctions wallet entries plus, for EVM, the rule-based wallet risk; for a person or company name use check_counterparty; for a list of addresses use sanctions_screening_batch. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `address` (string, required): The address you are about to pay: 0x EVM address or Solana address
- `url` (string): Optional endpoint URL: probed once to see if it answers 402 paying that same address

### `wallet_risk` (~203 tokens)

Wallet risk

Use for a rule-based risk label on an EVM address before paying it: exact sanctions match (OFAC SDN, UK and EU), contract or plain account (Base, Ethereum), outgoing transactions. Returns the paid x402 request for your input (GET /wallet/risk, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For an ERC-20 token use token_risk; for the sanctions match of many addresses (all screened lists) use sanctions_screening_batch; for one payee address before paying, including Solana, use check_payee. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `address` (string, required): EVM address (0x + 40 hex); ENS names are not resolved here
- `request_key` (string): Idempotency key, echoed back

### `token_risk` (~183 tokens)

Token risk

Use for a rule-based risk label on an ERC-20 token before you accept or route it: sanctions-list match (OFAC SDN, UK and EU), upgradeable proxy, owner with mint/pause/blacklist. Returns the paid x402 request for your input (GET /token/risk, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For a wallet (not a token contract) use wallet_risk. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `address` (string, required): Token contract address (0x + 40 hex)
- `chain` (string): Chain of the token; default base
- `request_key` (string): Idempotency key, echoed back

### `company_lei` (~197 tokens)

Company lei

Use when an agent needs to verify a company or find its LEI: by lei= the legal name, status, legal form, addresses, registration renewal date, direct and ultimate parent and BIC. Returns the paid x402 request for your input (GET /company/lei, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `country` (string): Optional 2-letter ISO country of the legal address to narrow a name search, e.g. DE.
- `lei` (string): 20-character Legal Entity Identifier (ISO 17442). Give lei or name.
- `name` (string): Company name to search (2-100 characters); returns up to 10 ranked matches. Give lei or name.

### `company_lei_batch` (~133 tokens)

Company lei batch

Use when you need to refresh or screen many companies by LEI (KYB, vendor or counterparty lists): up to 200 LEIs in one POST, read from GLEIF in one call: legal name, status, addresses. Returns the paid x402 request for your input (POST /company/lei/batch, $0.02 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge.

Input parameters:

- `leis` (array, required): 1 to 200 LEIs; duplicates are removed

### `lei_changes` (~222 tokens)

Lei changes

Use when you keep a KYB/LEI register and need what changed since your last run: legal-entity records created, lapsed. Returns the paid x402 request for your input (GET /lei/changes, $0.02 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `country` (string): Optional ISO country of the legal address, e.g. DE
- `limit` (integer): Records per page, default 50
- `page` (integer): Page of the newest-first list, default 1
- `since` (string, required): Date YYYY-MM-DD, at most 400 days back; records last updated on or after it
- `status` (string): Optional registration status: ISSUED, LAPSED, ANNULLED, PENDING_TRANSFER, PENDING_ARCHIVAL, DUPLICATE, RETIRED, MERGED

### `bank_us` (~167 tokens)

Bank us

Use when an agent needs to identify or vet a US bank: by name or FDIC cert returns FDIC data: active or closed, charter class, regulator, city/state, website, total assets and report date. Returns the paid x402 request for your input (GET /bank/us, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

Input parameters:

- `cert` (string): FDIC certificate number (1-6 digits). Use name or cert
- `name` (string): Bank name (phrase match; the largest active match is returned, others listed). Use name or cert

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 63
- 2026-11-08: 63
- 2026-11-07: 63

## Common questions

### What is the P0: sanctions, KYB and payee checks MCP server?

P0: sanctions, KYB and payee checks is an MCP server listed in the public MCP registry as dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sancti…. Sanctions screening, LEI lookup and payee checks for AI agents, pay per call over x402 or MPP. This page covers its hosted endpoint (https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance).

### Is the P0: sanctions, KYB and payee checks MCP server safe to use?

P0: sanctions, KYB and payee checks scores 70 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 P0: sanctions, KYB and payee checks MCP server expose?

P0: sanctions, KYB and payee checks exposes 11 tools: sanctions_screening, sanctions_screening_batch, sanctions_changes, check_counterparty, check_payee, and 6 more. Their descriptions and schemas cost roughly 2,223 tokens of context every time the server is loaded.

### Does the P0: sanctions, KYB and payee checks MCP server require authentication?

No. We connected to P0: sanctions, KYB and payee checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the P0: sanctions, KYB and payee checks MCP server still maintained?

P0: sanctions, KYB and payee checks 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 P0: sanctions, KYB and payee checks MCP server?

VerifyMCP ran 13 checks on P0: sanctions, KYB and payee checks, 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://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance
- Website: https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/tools#sanctions-kyb-compliance
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-x402-bazaar-rank-worker-x402-bazaar-rank-sanctions-kyb-compliance/mcp-sanctions-kyb-compliance
