Name: Verifex sanctions screening
Author: verifex

Verifex sanctions screening MCP

Screen people and companies against sanctions lists and fetch the Evidence Capsule audit record.

Grade A Local · stdio API key 3 tools v0.1.2 MIT

No reviews yet by verifexnpm Runs on your machine, nothing hosted

100/100

trust score

tools declared

local

runs on your machine

—

downloads a day

What it does

Screen people and companies against sanctions lists and fetch the Evidence Capsule audit record.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'VERIFEX_API_KEY=${VERIFEX_API_KEY}' --transport stdio verifex-sanctions-screening-mcp '--' npx -y verifex-mcp

# 2 — ask your agent for something these tools do
#   screen_name, get_screening, get_evidence_capsule

It needs VERIFEX_API_KEY: this reads it from your environment, so export it first.

Verifex sanctions screening costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

verifex1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Verifex sanctions screening as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads VERIFEX_API_KEY (Your Verifex secret API key (dashboard → API Keys). Screenings bill to your Verifex plan) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx VERIFEX_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'VERIFEX_API_KEY=${VERIFEX_API_KEY}' --transport stdio verifex-sanctions-screening-mcp '--' npx -y verifex-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: VERIFEX_API_KEY — Your Verifex secret API key (dashboard → API Keys). Screenings bill to your Verifex plan.. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Screen one person or company against the sanctions and watchlists on the caller's Verifex plan.

Parameter	Type	Required	Notes
name	string	yes	Full name of the person or company, on one line.
type	string	no	person, or entity for a company or organisation.
country	string	no	Two-letter ISO 3166-1 country code of nationality, residence or registration, e.g. AE, DE, RU.
date_of_birth	string	no	YYYY or YYYY-MM-DD. People only; narrows the candidates.

Return the stored record of an earlier screening on this account by its request_id, with its scope.

Parameter	Type	Required	Notes
request_id		yes	The request_id returned by screen_name.

Return the Evidence Capsule for a screening: the audit record of what was screened, which list versions were checked,

Parameter	Type	Required	Notes
capsule_id		yes	evidence_capsule_id from a screening (the same value as its request_id).

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Verifex sanctions screening or to call it, at any volume.

ATrust score 100 / 100

Release 0.1.2 · scanned 30 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score100

Findings0 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationsource

Surface digest76da192abaaa62f5df32e93378801d68f3a2f6e6e91881543b91c6bb622aa601

Score vectorthreat 100 → client 100

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfacenot available

Implementation sourceread

Package metadataread

Live transportnot available

No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
No per-tool rows for this release — see the note below.

No tool surface was enumerated, so there is nothing to attribute a capability to.

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest76da192abaaa62f5

Scanned2026-10-30

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.