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

io.github.cyanheads/sanctions-screening-mcp-server

REMOTE · SANCTIONS-SCREENING.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

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

+5 this week 72 Trust /100
Trust breakdown (6 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 →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1435 tokens (~205/item across 7 items; 6 tools + 1 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 Management27
  • Stability observed for 8 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · sanctions-screening.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-sanctions-screening-mcp-server https://sanctions-screening.caseyjhand.com/mcp
# ~/.codex/config.toml
[mcp_servers.cyanheads-sanctions-screening-mcp-server]
url = "https://sanctions-screening.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-sanctions-screening-mcp-server": {
      "type": "remote",
      "url": "https://sanctions-screening.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-sanctions-screening-mcp-server --url https://sanctions-screening.caseyjhand.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-sanctions-screening-mcp-server:
    url: "https://sanctions-screening.caseyjhand.com/mcp"
// mcp.json
{
  "mcpServers": {
    "cyanheads-sanctions-screening-mcp-server": {
      "type": "http",
      "url": "https://sanctions-screening.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 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.

  • 1 Aug 26 +1

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

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 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.

  • 28 Jul 26 +1

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

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 67

    First indexed and scored.

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 3 Aug 2026 · Probed https://sanctions-screening.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 7 Jul 2026 5 Oct 2026 ECDSA 256 ECDSA-SHA256 5aad900eb2055a0b0ea55912ec19680c
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC secure

Validation of sanctions-screening.caseyjhand.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
sanctions-screening.caseyjhand.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sanctions-screening.caseyjhand.com/mcp Verified 200
http (plaintext) http://sanctions-screening.caseyjhand.com/mcp HTTPS enforced 301 https://sanctions-screening.caseyjhand.com/mcp
MCP tools — 6 exposed · ~1,256 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.

Tool Tokens
sanctions_get_designation ~148

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.

NameTypeReqDescription
entryIdstringyesThe source list's own entry ID (the sourceEntryId from sanctions_screen_name).
sourcestringyesWhich source list the entry belongs to.
NameTypeReqDescription
addressesarrayyesPublished addresses.
aliasesarrayyesAll published aliases / name variants.
caveatstringyesDecision-support caveat — this is a screening aid, not a compliance determination.
datesOfBirtharrayyesPublished dates and places of birth (persons).
designationDatestringDesignation date, when published.
entityTypestringyesEntity classification as published.
identifiersarrayyesPublished identifiers (passport, national ID, tax, registration, …).
legalBasisstringStatutory / regulatory basis, when published.
nationalitiesarrayyesPublished nationalities / citizenships.
primaryNamestringyesPrimary published name.
programstringSanctioning program / regime, when published.
remarksstringFree-form remarks published by the source, when present.
sourcestringyesSource list the entry belongs to.
sourceEntryIdstringyesThe source list's own entry ID.
sourceLabelstringyesHuman-readable name of the source list.

No examples provided.

sanctions_get_entity ~142

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).

NameTypeReqDescription
leistringyesThe 20-character GLEIF Legal Entity Identifier to look up.
NameTypeReqDescription
caveatstringyesDecision-support caveat — the screening cross-reference is an aid, not a determination.
headquartersAddressstringSingle-line headquarters address, when published.
jurisdictionstringLegal jurisdiction (ISO code), when published.
lastUpdatestringISO 8601 last-update timestamp from the LEI record.
legalAddressstringSingle-line legal address, when published.
legalNamestringyesRegistered legal name.
leistringyesThe 20-character GLEIF Legal Entity Identifier.
otherNamesarrayyesOther / trading names published in the LEI record.
registrationAuthorityEntityIdstringThe entity's ID at its registration authority, when published.
registrationAuthorityIdstringRegistration authority (RA) code, when published.
sanctionsHitsarrayyesSanctions screening cross-reference on the entity's legal name.
statusstringRegistration status (e.g. ISSUED, LAPSED).

No examples provided.

sanctions_list_sources ~115

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
leiAsOfstringISO 8601 timestamp of the last completed GLEIF sync, when available.
leiReadybooleanyesTrue once the GLEIF (LEI) mirror has completed at least one full sync.
sanctionsAsOfstringISO 8601 timestamp of the last completed sanctions sync, when available.
sanctionsReadybooleanyesTrue once the sanctions mirror has completed at least one full sync.
sourcesarrayyesAll loaded sources, sanctions lists then the GLEIF dataset.

No examples provided.

sanctions_resolve_entity ~277

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.

NameTypeReqDescription
jurisdictionOptional ISO 3166-1 alpha-2 jurisdiction filter (e.g. "US", "GB"). Empty string disables it.
limitintegerMaximum LEI candidates to return.
matchModestringstrict (default): exact then all-tokens-present. fuzzy: also scored Jaro-Winkler.
minScorenumberJaro-Winkler floor for fuzzy hits (0–1); defaults to the server's configured floor.
namestringyesThe company / organization name to resolve to an LEI.
statusstringRegistration status filter: issued (default), lapsed, or any.
NameTypeReqDescription
matchModeUsedstringyesThe match mode actually applied (strict may upgrade to fuzzy).
matchesarrayyesRanked LEI candidates, highest-confidence first.
normalizedQuerystringyesThe name as the server folded it for matching.
noticestringGuidance when no LEI matched and how to broaden.
totalCountnumberyesNumber of LEI candidates returned.

No examples provided.

sanctions_screen_name ~351

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."

NameTypeReqDescription
entityTypestringRestrict to one entity class, or "any" (default) to screen across all.
limitintegerMaximum number of potential matches to return.
matchModestringstrict (default): exact-normalized then all-tokens-present. fuzzy: also scored Jaro-Winkler + phonetic. Strict auto-falls-back to fuzzy when it finds nothing.
minScorenumberScore floor for fuzzy hits (0–1), applied uniformly to every fuzzy candidate regardless of how it was matched (Jaro-Winkler, token, or phonetic). No hit below this score is returned. Applies to fuzzy…
namestringyesThe name to screen (person, organization, vessel, or aircraft).
sourcesarrayRestrict to specific source lists. Omit to screen all loaded lists.
NameTypeReqDescription
caveatstringyesDecision-support caveat — this is a screening aid, not a compliance determination.
hitsarrayyesScored potential matches, highest-confidence first.
matchModeUsedstringyesThe match mode actually applied (strict may auto-upgrade to fuzzy on empty).
normalizedQuerystringyesThe name as the server folded it for matching.
noticestringGuidance when no candidate matched — how to broaden, and what an empty result does NOT mean.
totalCountnumberyesNumber of potential matches returned.

No examples provided.

sanctions_trace_ownership ~223

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).

NameTypeReqDescription
depthintegerMaximum traversal depth from the root entity (1–5).
directionstringWalk parents (who owns it), children (what it owns), or both (default).
leistringyesThe 20-character GLEIF LEI at the root of the ownership graph.
screenNodesbooleanWhen true, screen every node's legal name against all watchlists for beneficial-ownership screening.
NameTypeReqDescription
caveatstringyesDecision-support caveat — node screening is an aid, not a determination.
edgesarrayyesDirected ownership edges between the nodes.
flaggedNodeCountnumberyesHow many screened nodes had at least one potential watchlist match.
nodesarrayyesAll entities reached in the traversal, including the root.
rootLeistringyesThe LEI the traversal started from.
screenedNodeCountnumberyesHow many nodes were screened (0 when screenNodes is false).

No examples provided.