MCP Tools DirectoryAbout this integration
Sanctions screening and PEP checks via OpenSanctions API for AI agents
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- opensanctions-mcp
- Last compatibility test
- Not independently tested
Connect your agent
opensanctions-mcpDocumented from hash-pinned publisher README and package manifest. No package or OpenSanctions endpoint was executed; screening output is informational and was not independently assessed.
Capabilities: Sanctions and PEP entity search, Structured entity matching, Compliance investigation summaries
Connected profiles
Additional details
io.github.scka-de/opensanctions-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17OPENSANCTIONS_API_KEY
Source ↗ · Checked 2026-09-17opensanctions-mcp
Source ↗ · Checked 2026-09-190.1.2
Source ↗ · Checked 2026-09-19The MCP client starts the executable npm package through npx and the running process forwards tool calls to the configured OpenSanctions API.
Source ↗ · Checked 2026-09-19The hosted OpenSanctions API requires OPENSANCTIONS_API_KEY for screening tools; dataset metadata tools and unauthenticated self-hosted yente instances are documented exceptions.
Source ↗ · Checked 2026-09-19The reviewed catalog connection remains stdio, launched by the MCP client as npx -y opensanctions-mcp with provider configuration in environment variables.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19