ZBS Index What actually exists in applied AI, with the source next to it

mcp server

sanctions-screening-mcp-server

Screen names against OFAC, EU, UK, UN sanctions lists; resolve entities via GLEIF. Screening aid.

Description as published by the maintainer. Source

  • version 0.1.7
  • active

active — Most recent push to the repository was 2026-07-30.

What this server can do

6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

sanctions_get_designation(source, entryId)
Fetch the full record for one sanctions designation by source list + entry ID — the drill-in after sanctions_screen_name surfaces a candidate. Returns all published aliases, identifiers (passport/national-ID/tax), addresses, dates and places of birth, nationalities, sanctioning program, legal basis, and designation date. The record reflects exactly what the source published; missing fields mean the source omitted them. This is a screening aid — the designation record supports a compliance review, it is not itself a determination. Required: source, entryId.
sanctions_get_entity(lei)
Fetch the full GLEIF Level 1 record for one LEI: legal name, other/trading names, legal and headquarters addresses, registration status, jurisdiction, registration authority and ID, and last-update date — plus any sanctions hits screened against the same legal name across all loaded watchlists. The screening cross-reference is a screening AID: a hit is a candidate to verify against the official source, and no hit is not a clearance. LEI must be a 20-character GLEIF identifier (18 alphanumerics + 2 check digits). Required: lei.
sanctions_list_sources
List the sanctions watchlists (OFAC SDN + Consolidated, EU, UK, UN) and GLEIF datasets currently loaded in the local mirror, each with its record count, source URL, license, and the mirror's readiness and as-of timestamp. Use this for provenance and freshness on any result — results are only as current as the last mirror refresh, and a not-ready mirror means screening cannot run yet. Attribution: UK data is under the Open Government Licence v3.0; all sources are cited here.
sanctions_resolve_entity(name, limit, status, minScore, matchMode, jurisdiction)
Resolve a company or organization name (with an optional ISO 3166-1 alpha-2 jurisdiction) to candidate GLEIF Legal Entity Identifiers (LEIs), ranked. This turns a free-text counterparty name into a stable global identifier that sanctions_get_entity and sanctions_trace_ownership key off. Strict mode (default) matches exact-normalized then all-tokens-present; fuzzy mode (or auto when strict is empty) adds Jaro-Winkler scoring labeled approximate with a raw 0–1 score. Returns potential matches to confirm against the GLEIF record — name resolution is a candidate ranking, not an authoritative identification. Required: name.
sanctions_screen_name(name, limit, sources, minScore, matchMode, entityType)
Screen a name (person, company, vessel, aircraft) against all loaded sanctions watchlists at once — OFAC SDN + Consolidated, EU, UK, and UN — alias- and fuzzy-aware. Returns scored potential matches with the source list, sanctioning program, designation date, and the matched alias. Strict mode (default) matches exact-normalized then all-tokens-present; fuzzy mode (or auto when strict is empty) adds Jaro-Winkler and phonetic matching and labels hits approximate with a raw 0–1 similarity score. This is a screening AID for a human/compliance review, NOT a compliance determination: a hit means "review this candidate against the official source," and an empty result never means "cleared." Required: name.
sanctions_trace_ownership(lei, depth, direction, screenNodes)
Trace the GLEIF Level 2 corporate-ownership graph for an LEI: direct and ultimate parents and/or children, traversed breadth-first to a bounded depth, with relationship type for each edge. Set screenNodes to also screen every entity in the graph against all loaded watchlists — beneficial-ownership screening that resolves "is anyone in this ownership chain sanctioned." Each per-node screen is a screening AID: hits are candidates to verify, and an empty result for a node is not a clearance of that node. Requires a valid 20-character LEI (use sanctions_resolve_entity to obtain one). Required: lei.

Last successful function declaration observed on . Source: https://sanctions-screening.caseyjhand.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://sanctions-screening.caseyjhand.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 1 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-07-30 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 9 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 0.1.7 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-07-05 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License Apache-2.0 Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-07-05 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 6 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe sanctions-screening.caseyjhand.com
mcp endpoint status ok The server listed 6 functions when asked. as of probe sanctions-screening.caseyjhand.com

Where to get it

Related, by what their authors tagged them

  • io.github.Deep-Identity-Inc/agent-skill — last commit 2026-07-13, shares aml, kyc, sanctions
    An MCP Server that provides identity verification and anti-fraud tools for AI agents via deepidv.
  • OnchainDiligence — last commit 2026-07-08, shares sanctions
    Pay-per-call compliance via x402: wallet sanctions, OFAC name, UK + US company verification.
  • Brazilayer — Brazilian Public Data — last commit 2026-07-27, shares sanctions
    Brazilian company registry (CNPJ) + sanctions screening for AI agents. Pay per call via x402.
  • dev.cz-agents/adis — last commit 2026-08-03, shares due-diligence, kyc
    Czech VAT-payer reliability (ADIS / nespolehlivý plátce DPH) + registered bank accounts by DIČ.
  • dev.cz-agents/ares — last commit 2026-08-03, shares due-diligence, kyc
    Czech & Slovak business registry — company lookup by IČO, name, legal form, VAT. Official ARES.
  • dev.cz-agents/cnb — last commit 2026-08-03, shares due-diligence, kyc
    Official ČNB exchange rates — daily & historical CZK vs EUR, USD, 30+ currencies. For accounting.
  • dev.cz-agents/dd — last commit 2026-08-03, shares due-diligence, kyc
    Czech & EU due diligence in one call — facts, insolvency, sanctions, VAT, risk score, UBO chain.
  • dev.cz-agents/eu-registry — last commit 2026-08-03, shares due-diligence, kyc
    EU company registry lookup across 16 countries incl. Sweden Bolagsverket.
  • dev.cz-agents/isir — last commit 2026-08-03, shares due-diligence, kyc
    Czech insolvency register (ISIR) — active/historical insolvency & bankruptcy by IČO or person.
  • dev.cz-agents/payqr — last commit 2026-08-03, shares due-diligence, kyc
    European payment QR — SPAYD (CZ/SK) & EPC/GiroCode (SEPA), plus text/WiFi/vCard. Local, free.

These share tags the maintainers applied themselves, such as aml, kyc, sanctions, due-diligence. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

Also from cyanheads

How the author describes it

Topics the maintainer set on GitHub: ai-agents, aml, bun, compliance, cyanheads, due-diligence, gleif, kyc, lei, mcp, mcp-server, model-context-protocol, ofac, sanctions, screening, typescript.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. cyanheads/sanctions-screening-mcp-server on GitHub — GitHub, observed , trust tier 3.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.
  3. Tools declared by the MCP server at https://sanctions-screening.caseyjhand.com/mcp — sanctions-screening.caseyjhand.com, observed , trust tier 4.