Opensanctions MCP server
Sanctions screening and PEP checks via OpenSanctions API for AI agents
0 stars
Reviews
Write oneNobody has reviewed Opensanctions yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Opensanctions tools (6, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
get_datasetGet full details about a specific dataset: description, publisher, entity count, last updated, and coverage information. No API key required. Use list_datasets first to find dataset names, then this tool for details.
get_entityFetch complete details for a specific entity by ID, including all properties, dataset memberships, and relationships to other entities. Use this after finding an entity via search or match to get the full picture: aliases, addresses, birth dates, related companies, family members, associates. Relationships come from the OpenSanctions knowledge graph. Types include: ownershipOwner, familyRelative,
investigate_entitywrite actionRun a multi-step compliance investigation on a person or company. This is the most powerful tool \u2014 it combines matching, entity details, and relationship traversal in one call. Steps: (1) Match the name against sanctions/PEP lists, (2) Fetch full details and relationships for top matches, (3) Return structured data with scores, datasets, and connected entities. Returns data only \u2014 no ris
list_datasetsList available sanctions and PEP datasets in OpenSanctions. No API key required. Returns dataset names, titles, summaries, and entity counts. Use the optional query parameter to filter. Examples of datasets: "us_ofac_sdn" (US OFAC), "eu_fsf" (EU Financial Sanctions), "un_sc_sanctions" (UN Security Council), "gb_hmt_sanctions" (UK HMT).
match_entityScreen a person or company against sanctions and PEP (Politically Exposed Person) lists using structured properties. This is the primary screening tool. Provide a schema type and properties for precise matching. The matching algorithm uses name comparison, birth dates, nationalities, and identifiers for scoring. Scores: 0.0-1.0. Above 0.9 = very high confidence match. 0.7-0.9 = likely match, inves
search_entitiesSearch the OpenSanctions database by name or keyword. Returns matching entities ordered by relevance. Use this for exploratory queries: "find entities named Goldman", "search for companies in Russia". For formal sanctions screening with confidence scores, use match_entity instead. Results include entity type, datasets (which sanctions lists), and properties. For numeric match scores, use match_ent
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 180 days ago4/15
- Maintainer identityregistry namespace matches repository owner6/10
Install Opensanctions in Claude Code, Cursor or VS Code
Runs npx -y opensanctions-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add opensanctions-mcp -- npx -y opensanctions-mcp
Opensanctions: common questions
- Is Opensanctions MCP server safe?
- With care: it is graded C, so read the findings first (63/100). Read the Opensanctions safety report
- How do I install Opensanctions?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Opensanctions need an API key?
- Yes. The registry entry asks for
OPENSANCTIONS_API_KEY. - Is Opensanctions maintained?
- The last commit was 196 days ago (2026-03-31). The latest release is v0.1.1.