Sanctions Screening Skill

What this skill does

Give your agent OFAC sanctions screening. Call it as an MCP tool to check any name against the SDN list and get scored matches with aliases and programs. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Sanctions Screening Skill — exactly what your agent gets back when it makes the call.

vervekit · sanctionscreeningtool call

{ }

result

query: Banco Nacional de Cuba
matched: true
matchCount: 1
verdict: exact
topScore: 1
results: [ 1 item ]
list: { … }

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Live data, no endpoint wiring

Enable Sanctions Screening and your app can add sanctions screening to your app through one connection — no client library for a finance API, no keys to rotate per provider. The skill answers over MCP or REST using the key you already have.

A tool your agent reaches for

Over MCP, Sanctions Screening shows up as the sanctionscreening tool your model calls whenever a task needs live numbers — it decides when, you don't write the glue.

Ship it in an afternoon

Flip the skill on and call it from your backend the same day; there's nothing to deploy and nothing to maintain as the underlying data changes.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

sanctionscreening

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/sanctionscreening

Ask your agent

“Enable Sanctions Screening and ask your agent to add sanctions screening to your app.”
“What's the latest price and how has it moved today?”

Sanctions Screening Skill, answered

How to connect it over MCP or REST.

How do I add Sanctions Screening to my app or agent?

Enable the Sanctions Screening Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the sanctionscreening tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add sanctions screening to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Sanctions Screening appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Sanctions Screening call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Sanctions Screening is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Sanctions Screening is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Live data, no endpoint wiring

A tool your agent reaches for

Ship it in an afternoon

Sanctions Screening Skill, answered

Give your software a way to act on the world.

Scaling in production?