Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

+4 this week 70 Trust /100

Last scanned (21 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • Tool “company_lei_batch” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +1
    • 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 security
    • Schema quality: 282 → 221 ▲ functional
    • Schema quality: good → excellent functional
  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=x402-bazaar-rank-worker.workers.dev CN=YE2,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 6c09b073fe5d3fd83fd987465725765b6e5
SANs: *.x402-bazaar-rank-worker.workers.dev, x402-bazaar-rank-worker.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance Verified 200
http (plaintext) http://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance Served over HTTP 200
MCP tools · 11 exposed · ~2,223 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bank_us ~167

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.

NameTypeReqDescription
certstring–FDIC certificate number (1-6 digits). Use name or cert
namestring–Bank name (phrase match; the largest active match is returned, others listed). Use name or cert

No output schema declared.

No examples provided.

check_counterparty ~243

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.

NameTypeReqDescription
addressstring–Optional crypto wallet address to screen too
countrystring–Optional ISO country, e.g. DE (non-US skips the FDIC section)
leistring–Optional 20-character LEI: read instead of a name search
namestringyesCounterparty name in Latin letters

No output schema declared.

No examples provided.

check_payee ~218

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.

NameTypeReqDescription
addressstringyesThe address you are about to pay: 0x EVM address or Solana address
urlstring–Optional endpoint URL: probed once to see if it answers 402 paying that same address

No output schema declared.

No examples provided.

company_lei ~197

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.

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

No output schema declared.

No examples provided.

company_lei_batch ~133

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.

NameTypeReqDescription
leisarrayyes1 to 200 LEIs; duplicates are removed

No output schema declared.

No examples provided.

lei_changes ~222

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.

NameTypeReqDescription
countrystring–Optional ISO country of the legal address, e.g. DE
limitinteger–Records per page, default 50
pageinteger–Page of the newest-first list, default 1
sincestringyesDate YYYY-MM-DD, at most 400 days back; records last updated on or after it
statusstring–Optional registration status: ISSUED, LAPSED, ANNULLED, PENDING_TRANSFER, PENDING_ARCHIVAL, DUPLICATE, RETIRED, MERGED

No output schema declared.

No examples provided.

sanctions_changes ~206

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.

NameTypeReqDescription
limitinteger–Events per page, default 100
listsstring–Optional comma list of ofac, uk, eu, ca, csl; default all
offsetinteger–Events to skip (newest first), default 0
sincestringyesDate YYYY-MM-DD: changes in list versions dated on or after it (log keeps 90 days)

No output schema declared.

No examples provided.

sanctions_screening ~299

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.

NameTypeReqDescription
addressstring–crypto address to screen (send this or name)
limitinteger–name matches only: max hits
min_scorenumber–name matches only: lowest similarity score to report
namestring–person or entity name in Latin letters (transliterated), at least one word of 3+ characters (send this or address)

No output schema declared.

No examples provided.

sanctions_screening_batch ~152

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.

NameTypeReqDescription
addressesarrayyes1 to 25 crypto addresses to screen (as written on their chains); duplicates are removed; names are not accepted

No output schema declared.

No examples provided.

token_risk ~183

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.

NameTypeReqDescription
addressstringyesToken contract address (0x + 40 hex)
chainstring–Chain of the token; default base
request_keystring–Idempotency key, echoed back

No output schema declared.

No examples provided.

wallet_risk ~203

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.

NameTypeReqDescription
addressstringyesEVM address (0x + 40 hex); ENS names are not resolved here
request_keystring–Idempotency key, echoed back

No output schema declared.

No examples provided.

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.

remote · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev

# add to Claude Code
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'
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.