Skip to content

P0: sanctions, KYB and payee checks MCP server

dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sanctions-kyb-compliancex402-bazaar-rank.x402-bazaar-rank-worker.workers.devstreamable-httpv1.0.2Scanned

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

11 tools: 11 change things.

Tools: 0 delete, 0 irreversible, 11 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 11
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

11 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the P0: sanctions, KYB and payee checks MCP server can do

The P0: sanctions, KYB and payee checks MCP server is published by x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev, a domain the MCP Registry verified. It has 11 tools. It can create or change data (11 tools: sanctions_screening, sanctions_screening_batch, sanctions_changes, check_counterparty and 7 more), but cannot delete data. None of its tools only reads.

11 tools bring in text other people can write (sanctions_screening, sanctions_screening_batch, sanctions_changes and 8 more); 1 tool can send data out of your system (check_payee).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 11Claude Code: ask
  • bank_usUse 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 repo…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bank us
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_counterpartyUse 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check counterparty
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_payeeUse 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).Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check payee
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • company_leiUse 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Company lei
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • company_lei_batchUse 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, addre…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. First call each day returns the data itself, free; later calls return the paid request.

    Annotations the server declares

    • title: Company lei batch
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • lei_changesUse when you keep a KYB/LEI register and need what changed since your last run: legal-entity records created, lapsed.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Lei changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • sanctions_changesUse 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,…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Sanctions changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • sanctions_screeningUse 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 Cana…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Sanctions screening
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • sanctions_screening_batchUse 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).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Sanctions screening batch
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • token_riskUse 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Token risk
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • wallet_riskUse 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Wallet risk
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write11
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:25 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance: tools/list returned 11 tools to an anonymous client, including sanctions_screening (write), sanctions_screening_batch (write), sanctions_changes (write), check_counterparty (write), check_payee (write) and 6 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools11 changed.~11 changedView diff
  2. Tools11 changed.~11 changedView diff

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http sanctions-kyb-compliance https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance
claude mcp add --transport http sanctions-kyb-compliance https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sanctions-kyb-compliance

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__sanctions-kyb-compliance__sanctions_screening",
      "mcp__sanctions-kyb-compliance__sanctions_screening_batch",
      "mcp__sanctions-kyb-compliance__sanctions_changes",
      "mcp__sanctions-kyb-compliance__check_counterparty",
      "mcp__sanctions-kyb-compliance__check_payee",
      "mcp__sanctions-kyb-compliance__wallet_risk",
      "mcp__sanctions-kyb-compliance__token_risk",
      "mcp__sanctions-kyb-compliance__company_lei",
      "mcp__sanctions-kyb-compliance__company_lei_batch",
      "mcp__sanctions-kyb-compliance__lei_changes",
      "mcp__sanctions-kyb-compliance__bank_us"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sanctions-kyb-compliance. Review it before you use it.

Capability tags behind 11 rules
  • mcp__sanctions-kyb-compliance__sanctions_screening untrusted-input
  • mcp__sanctions-kyb-compliance__sanctions_screening_batch untrusted-input
  • mcp__sanctions-kyb-compliance__sanctions_changes untrusted-input
  • mcp__sanctions-kyb-compliance__check_counterparty untrusted-input
  • mcp__sanctions-kyb-compliance__check_payee untrusted-input, outbound
  • mcp__sanctions-kyb-compliance__wallet_risk untrusted-input
  • mcp__sanctions-kyb-compliance__token_risk untrusted-input
  • mcp__sanctions-kyb-compliance__company_lei untrusted-input
  • mcp__sanctions-kyb-compliance__company_lei_batch untrusted-input
  • mcp__sanctions-kyb-compliance__lei_changes untrusted-input
  • mcp__sanctions-kyb-compliance__bank_us untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sanctions-kyb-compliance/verify?hash=492be331f43c8320a2bfdadfc526c3e27527355b095f6b6e4c78a528a2792d93" | jq -e '.changed == false'

Pinned hash 492be331f43c, from Nov 13, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sanctions-kyb-compliance/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sanctions-kyb-compliance
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sanctions-kyb-compliance.svg)](https://radar.anlyon.com/servers/dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sanctions-kyb-compliance)

Source: MCP Registry. Synced Nov 13, 2026, 14:17 UTC.

P0: sanctions, KYB and payee checks MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 11 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the P0: sanctions, KYB and payee checks MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the P0: sanctions, KYB and payee checks MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the P0: sanctions, KYB and payee checks MCP server have?

11 tools: 11 write. sanctions_screening, sanctions_screening_batch, sanctions_changes, check_counterparty, check_payee, wallet_risk, token_risk, company_lei and 3 more.

Does the P0: sanctions, KYB and payee checks MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the P0: sanctions, KYB and payee checks MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_payee.

Has the P0: sanctions, KYB and payee checks MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.