Sanctions screening: OFAC, UK, EU, UN MCP server
io.github.Bosco-Labs/sanctions-screeningBosco-Labsstreamable-httpv1.0.3Scanned
Screen names and crypto wallets against OFAC SDN, UK, EU and UN sanctions lists, with list dates
4 tools: 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Sanctions screening: OFAC, UK, EU, UN MCP server can do
The Sanctions screening: OFAC, UK, EU, UN MCP server is published by the GitHub account Bosco-Labs. It has 4 tools. It can create or change data (3 tools: run_records_plan, check_counterparty and screen_sanctions), but cannot delete data. 1 tool only reads.
3 tools bring in text other people can write (run_records_plan, check_counterparty and screen_sanctions).
The fixed checks matched 3 findings (annotation-conflict and base64-blob). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.3.
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.
4 tools
Changes things 3Claude Code: ask
check_counterpartyCan I do business with this company?Reads text others write1 finding
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.
Findings
- Warn
The input schema at properties.walletAddresses.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.walletAddresses.description: "...be paid on, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]"
Description, as the server wrote it Can I do business with this company? One call checks a supplier, customer or partner against official sources and returns a checklist: pass, fail, review or unverified per check, each with its source link and time. Built for AI agents doing KYB, vendor onboarding or "may I pay this party?" checks, and for people who want a fast, sourced first screen. To screen a vendor list, pass up to 10 companies in `companies`: one checklist per company, same price each. Needs `query` (a company name or registration number) or `companies` (up to 10). For names or crypto wallets against sanctions lists only, use screen_sanctions ($0.01); for a company profile with its financials, use get_company_profile. Price: $0.05 per `counterparty-check`.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Counterparty Check API: KYB, sanctions screening, insolvency
run_records_planRuns a plan from plan_records_query (its plan_id) or explicit steps, all steps in parallel, under a hard max_usd: if the worst case could exceed it, nothing runs.Reads text others write1 finding
Why it is in this group
- The name "run_records_plan" says "run": a word for a change.
- 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.
Findings
- Warn
The server marks "run_records_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "run_records_plan" says "run": a word for a change.
Description, as the server wrote it Runs a plan from plan_records_query (its plan_id) or explicit steps, all steps in parallel, under a hard max_usd: if the worst case could exceed it, nothing runs. Each step is charged to the caller's key exactly like a direct tool call (failed steps are free). Returns one section per step (via_tool, via_input, rows with source_url), a receipt and the citations. Reaches all 30 tools; to list them as MCP tools, add ?tools=all to the MCP URL.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: true
- title: Run an official-records plan
screen_sanctionsAnswers "is this company, vessel or person sanctioned?" for one or many names, against the official OFAC SDN and non-SDN lists, the US Consolidated Screening List (Commerce Entity …Reads text others write1 finding
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.
Findings
- Warn
The input schema at properties.addresses.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.addresses.description: "...e per entry, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]"
Description, as the server wrote it Answers "is this company, vessel or person sanctioned?" for one or many names, against the official OFAC SDN and non-SDN lists, the US Consolidated Screening List (Commerce Entity List, Denied Persons, State lists), the UK Sanctions List, the EU financial sanctions list and the UN Security Council list. Every answer says which lists were checked and how current they were, and every match links to its official source. Built for AI agents doing KYB, compliance or procurement checks, and for people who need a quick, sourced screen. It also checks crypto wallet addresses exactly against the addresses OFAC lists (XBT, ETH, USDT, TRX and more), e.g. before an agent pays. Needs `names` or `addresses` (crypto wallets). Lists only: for a full supplier check (register status, insolvency, VAT and IBAN as well as sanctions), use check_counterparty. Price: $0.01 per `name-screened`.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Sanctions List Screening API: OFAC, UK, EU, UN & US lists
Only reads 1Show 1 read-only tool
plan_records_queryFree, no key needed.No findings
Why it is in this group
- The name "plan_records_query" says "query": a word for reading.
Description, as the server wrote it Free, no key needed. Turns a question in plain words into the exact typed Bosco Labs calls that answer it: tool, input, why, and the maximum price of each step, plus what is not covered. Pass the user's question verbatim AND the entities you extracted from it (company_names, tickers, identifiers, countries, dates, law references...): the planner trusts your entities over its own parsing and puts them in the right input fields. The plan echoes them in entities_used and lists in `missing` what to pass for a better plan. Rules and examples first; only when they are unsure and you passed no entities does a small AI step extract the entities (budget-capped, marked `assisted`). Same steps, same plan_id. Run it with run_records_plan (paid, max_usd) or call the listed tools directly. Low confidence returns the top 3 candidate tools instead. Questions are kept 30 days in a cut-down form; leave out personal details.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Plan an official-records query
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 or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 16, 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
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.boscolabs.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.boscolabs.dev/mcp?tools=sanctions_screening,counterparty_check,plan_official_records_query: tools/list returned 3 tools to an anonymous client, including counterparty_check (write), sanctions_screening (write)
Posture changes
- Nov 16, 2026
- Tools that change things, listed without credentials: 0 to 2
- RFC 9728 protected resource metadata: https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp/free to https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp
Findings
Matches of fixed checks, with the text they matched.
- Warnrun_records_plan
The server marks "run_records_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "run_records_plan" says "run": a word for a change.
The input schema at properties.walletAddresses.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.walletAddresses.description: "...be paid on, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]"
- Warnscreen_sanctions
The input schema at properties.addresses.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.addresses.description: "...e per entry, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]"
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 added, 3 removed.+4 added−3 removedView diff
- Added:check_counterpartyChanges things
- Added:plan_records_queryOnly reads
- Added:run_records_planChanges things
- Added:screen_sanctionsChanges things
- Removed:counterparty_check
- Removed:plan_official_records_query
- Removed:sanctions_screening
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 2; RFC 9728 protected resource metadata: https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp/free -> https://api.boscolabs.dev/.well-known/oau…View diff
- Tools that change things, listed without credentials: 0 to 2
- RFC 9728 protected resource metadata: https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp/free to https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp
Tools2 added, 3 removed, 1 changed.+2 added−3 removed~1 changedView diff
- Added:counterparty_checkChanges things
- Added:sanctions_screeningChanges things
- Removed:describe_official_records_tool
- Removed:lei_lookup
- Removed:sec_company_lookup
- Changed:plan_official_records_queryOnly readsinputSchema
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http sanctions-screening https://api.boscolabs.dev/mcp?tools=screen_sanctions,check_counterparty,plan_records_query --header 'Authorization: <your-authorization>'claude mcp add --transport http sanctions-screening https://api.boscolabs.dev/mcp?tools=screen_sanctions,check_counterparty,plan_records_query --header 'Authorization: <your-authorization>'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.
{
"permissions": {
"allow": [
"mcp__sanctions-screening__plan_records_query"
],
"ask": [
"mcp__sanctions-screening__run_records_plan",
"mcp__sanctions-screening__check_counterparty",
"mcp__sanctions-screening__screen_sanctions"
],
"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-screening. Review it before you use it.
Capability tags behind 3 rules
- mcp__sanctions-screening__run_records_plan untrusted-input
- mcp__sanctions-screening__check_counterparty untrusted-input
- mcp__sanctions-screening__screen_sanctions 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/io.github.Bosco-Labs/sanctions-screening/verify?hash=19268178ba006a7ed19b7396ae7bbd2e5a00f561d237227fe3dd0b0bfbdce23d" | jq -e '.changed == false'Pinned hash 19268178ba00, from Nov 17, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Bosco-Labs/sanctions-screening/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Bosco-Labs/sanctions-screening)Source: MCP Registry · repository. Synced Nov 17, 2026, 21:17 UTC.
Sanctions screening: OFAC, UK, EU, UN MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Sanctions screening: OFAC, UK, EU, UN MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 3 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 Sanctions screening: OFAC, UK, EU, UN MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Sanctions screening: OFAC, UK, EU, UN 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 Sanctions screening: OFAC, UK, EU, UN MCP server have?
- 4 tools: 3 write, 1 read. run_records_plan, check_counterparty, screen_sanctions and plan_records_query.
Does the Sanctions screening: OFAC, UK, EU, UN MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Sanctions screening: OFAC, UK, EU, UN MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Sanctions screening: OFAC, UK, EU, UN MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.