Skip to content
MCP server

Verifex sanctions screening

Screen people and companies against sanctions lists and fetch the audit record

Runs locallyStatus and history
Install
Pricing
Free trial
Platforms
CLI, API
Runs
Locally
Version
0.1.2
Listing updated
3 days ago

About Verifex sanctions screening

Verifex sanctions screening is an MCP server for security. It runs locally on your machine and is started by your AI client.

Result wording is deliberately cautious. Every answer starts with a status line: potential match with review required, no potential match in the lists checked, screening incomplete with do-not-treat-as-clear, or review required because a stored record carries no decision. The server only adds caution to Verifex's decision, never removes it, and a clean result is explicitly not a statement that someone is on no list anywhere.

The server runs locally over stdio on Node.js 18.17 or later and uses your own Verifex API key, so screenings bill to your plan. It sends Verifex only the name, type, country and date of birth. Tools let an assistant screen a party, read back a past screening with get_screening, and fetch its Evidence Capsule, the record of what was checked and found. On the Free plan only OFAC and UN lists are screened, so a no-match result there reads as incomplete.

The docs advise creating a separate API key for the MCP client because a key has full access to the account's API. Plans include 5 free trial screens, with Starter at 2,500 screens a month and screening records kept for 10 years by default.

Install

Run in a terminal

claude mcp add screening --env VERIFEX_API_KEY='<VERIFEX_API_KEY>' -- npx -y verifex-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "screening": {
      "command": "npx",
      "args": [
        "-y",
        "verifex-mcp"
      ],
      "env": {
        "VERIFEX_API_KEY": "<VERIFEX_API_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "screening": {
      "command": "npx",
      "args": [
        "-y",
        "verifex-mcp"
      ],
      "env": {
        "VERIFEX_API_KEY": "<VERIFEX_API_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "screening": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "verifex-mcp"
      ],
      "env": {
        "VERIFEX_API_KEY": "<VERIFEX_API_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "screening": {
      "command": "npx",
      "args": [
        "-y",
        "verifex-mcp"
      ],
      "env": {
        "VERIFEX_API_KEY": "<VERIFEX_API_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "screening": {
      "command": "npx",
      "args": [
        "-y",
        "verifex-mcp"
      ],
      "env": {
        "VERIFEX_API_KEY": "<VERIFEX_API_KEY>"
      }
    }
  }
}

Configuration

  • VERIFEX_API_KEYYour Verifex secret API key (dashboard → API Keys). Screenings bill to your Verifex plan.Required
  • VERIFEX_API_URLAPI origin. Leave unset for https://api.verifex.dev.

Tools this server provides (1)

Taken from the project documentation; the running server may differ.

get_screening
Reads back a stored screening.

What it does

Cautious status lines
Results state whether review is required, no match was found, or screening was incomplete.
Scope statement
Each result names the lists that were and were not checked.
Evidence Capsule
Fetches the audit record of what was checked and found.
Past screening lookup
get_screening reads back an earlier screening.
Minimal data sent
Only name, type, country and date of birth go to Verifex.
Local stdio server
Runs on your machine with no other dependencies.

Good for

  • Screen a new customer or vendor from a chat
  • Read back an earlier screening for a file
  • Attach an audit record to a compliance review
  • Check why a result was incomplete
  • Run quick name checks during onboarding

Pricing

Free trial

5 free screens, then paid plans in EUR; about 0.02 EUR per screen at Starter

Prices change. Check verifex.dev before you buy.

Verifex sanctions screening FAQ

What does it need?

A Verifex API key and Node.js 18.17 or later.

Is a no-match result a clearance?

No. It only means nothing was found in the lists named underneath.

Is there a free trial?

Yes: 5 free screens with no card, and a 7-day trial on Starter, Growth and Pro.

Which lists does the Free plan check?

OFAC and UN only, so results without matches read as incomplete.

Is Verifex sanctions screening free?

Verifex sanctions screening is a paid product with a free trial.

How do I add Verifex sanctions screening to Claude Code?

Run this command in your terminal: claude mcp add screening --env VERIFEX_API_KEY='<VERIFEX_API_KEY>' -- npx -y verifex-mcp

What are the best alternatives to Verifex sanctions screening?

The closest alternatives to Verifex sanctions screening are REA, Agent Roast, Midplane, Leash and Tinplate Edge AI Safety, Security & EU Compliance.

Alternatives to Verifex sanctions screening

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Agent Roast

    MCP server

    Offline review that flags agent changes which weaken tests, assertions or CI

    Runs locally
    • Open source
    • 4 Hacker News points
    • Developer tools
  3. Midplane

    MCP server

    Postgres gateway for AI agents with table grants, column masking and approval for writes

    Runs locally
    • Open source
    • 5 GitHub stars
    • Databases
  4. Leash

    MCP server

    Review what your AI touched, approve risky actions and undo supported changes

    • 1 tool
    • Remote
    • Free
    • 1 GitHub star
    • Security
  5. SecureCloud

    MCP server

    SentinelOne and IT security catalog, prices, quotes and checkout links for Israel

    • 7 tools
    • Remote
    • Free
    • Security