Verifex sanctions screening — Claude Code MCP server
Verifex sanctions screening runs sanctions checks on individuals or companies via Verifex and fetches Evidence Capsule audit trails inside your coding agent.
MIT ★ 1 updated 2026-10-28
claude mcp add --env VERIFEX_API_KEY=<VERIFEX_API_KEY> --env VERIFEX_API_URL=<VERIFEX_API_URL> --transport stdio verifex-sanctions-screening -- npx -y verifex-mcpWhat Verifex sanctions screening does
The server communicates locally via stdio using npx and forwards strictly four fields to the Verifex API: name, entity type, country code, and date of birth. It exposes three operations: screening a party with screen_name, looking up earlier results with get_screening, and retrieving an Evidence Capsule audit record through get_evidence_capsule.
Responses display a clear status indicator followed by the screened jurisdictions. On the Free tier, Verifex inspects only OFAC and UN records, so clean hits still yield an incomplete status due to missing EU and UK coverage.
Execution requires Node.js 18.17 or higher alongside a valid VERIFEX_API_KEY. The server enforces a baseline cap of 20 screenings per 10 minutes to protect your balance from unintended runaway calls.
What it helps with
- screen business partners against international sanctions rosters
- retrieve an Evidence Capsule audit record by request ID
- inspect past screening logs without deducting fresh balance
- rate-limit automated screening calls to protect account credits
Example prompts for the agent
- Screen Acme Trading FZE from the UAE and display which sanction databases were evaluated
- Fetch the Evidence Capsule for screening scr_12345 to include in our compliance log
- Look up stored screening record scr_98765 and report its current state
How to install Verifex sanctions screening
Platform CLI
claude mcp add --env VERIFEX_API_KEY=<VERIFEX_API_KEY> --env VERIFEX_API_URL=<VERIFEX_API_URL> --transport stdio verifex-sanctions-screening -- npx -y verifex-mcpReplace <…> with your own values
Platform CLI
codex mcp add verifex-sanctions-screening --env VERIFEX_API_KEY=<VERIFEX_API_KEY> --env VERIFEX_API_URL=<VERIFEX_API_URL> -- npx -y verifex-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"verifex-sanctions-screening": {
"command": "npx",
"args": [
"-y",
"verifex-mcp"
],
"env": {
"VERIFEX_API_KEY": "<VERIFEX_API_KEY>",
"VERIFEX_API_URL": "<VERIFEX_API_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"verifex-sanctions-screening": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"verifex-mcp"
],
"env": {
"VERIFEX_API_KEY": "<VERIFEX_API_KEY>",
"VERIFEX_API_URL": "<VERIFEX_API_URL>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e VERIFEX_API_KEY=<VERIFEX_API_KEY> -e VERIFEX_API_URL=<VERIFEX_API_URL> verifex-sanctions-screening npx -y verifex-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Verifex sanctions screening
How to install Verifex sanctions screening in Claude Code?
Run `claude mcp add --env VERIFEX_API_KEY=<VERIFEX_API_KEY> --env VERIFEX_API_URL=<VERIFEX_API_URL> --transport stdio verifex-sanctions-screening -- npx -y verifex-mcp in your terminal. Replace <VERIFEX_API_KEY> and <VERIFEX_API_URL>` with your credentials.
What information leaves my machine during a screening?
The tool sends only the query name, entity category, country code, and birth date. Your private token stays in transport headers and never enters agent context or logs.
Why does the tool report Screening incomplete on clean lookups?
This flag appears whenever mandatory databases like EU or UK were skipped. Free accounts only process OFAC and UN lists, preventing the engine from confirming full clearance.