Skip to content
SanctionListCheck logo

SanctionListCheck MCP server

Which servers in the official MCP registry are SanctionListCheck's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to SanctionListCheck

Whose server it is
  • Registry namecom.sanctionlistcheck/sanctionlistcheckverified in the MCP registry

The registry name sits under sanctionlistcheck.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools4
  • Server calls itselfsanctionlistcheck
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 91 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Check customer names against official sanctions lists", the likely first call is screen_names.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-20
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer674 ms
  • Space in an agent's context≈ 616 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Check customer names against official sanctions lists
  • not sure · Keep dated screening records for due diligence files
  • not sure · Review possible matches row by row before a shipment

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-20
  • screen_names

    Audit-ready sanctions screening of 1 to 100 names against 10 official lists. The response includes a record id, the snapshot version, the data-as-of date for each source list, and the matching engine version. Each screened name costs one…

  • get_record

    Fetch a previously stored screening record by its record id. This tool is free to use.

  • list_sources

    The list_sources tool provides the 10 official sanctions lists and their data-as-of dates from the current daily snapshot. This tool is free to use and does not require an API key.

  • get_balance

    Retrieve the credit balance for your API key and its latest credit movements. This tool is free to use.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "sanctionlistcheck": {
      "type": "http",
      "url": "https://sanctionlistcheck.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http sanctionlistcheck https://sanctionlistcheck.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://sanctionlistcheck.com/mcp as a custom connector in the settings.

OpenAPI spec

8 paths, read 2026-10-20. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.