Sanctions Screening ServerVerified🛡 No advisories
Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/cyanheads, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
About
Screen names against OFAC, EU, UK, UN sanctions lists; resolve entities via GLEIF. Screening aid.
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸sanctions_screen_name100A
▸sanctions_get_designation100A
▸sanctions_list_sources100A
▸sanctions_resolve_entity100A
▸sanctions_get_entity100A
▸sanctions_trace_ownership100A
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +16 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
Already earned (4) ▾Already earned (4) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.cyanheads/sanctions-screening-mcp-server)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"sanctions_screening_mcp_server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/sanctions-screening-mcp-server"
]
}
}
}▶ Try itlive against sanctions-screening.caseyjhand.com
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.