Connect

EU Counterparty Sanctions Preflight

Screen a counterparty against the EU consolidated financial sanctions list, with a vocabulary that never turns a no-match into clearance.

1 · Your account

Sign in and you will come straight back to this page, still on EU Counterparty Sanctions Preflight. If you do not have an account yet, signing up creates one — no card, no application.

2 · What you can spend

Your workspace has one free allowance of 25 accepted calls, valid 14 days from the moment you create your first key — not 25 per server. If you have already connected another server, that is where the allowance sits, and calls here are charged from your balance. Your money balance covers every Jithox MCP server; a failed, refused or rate-limited call never spends anything.

3 · Your key

Your MCP client authenticates with a credential this workspace owns. Jithox shows it to you once — only its fingerprint is stored, so it is never logged, never put in a URL and never readable again. If you lose it, replace it; nobody can recover it for you, including us.

Sign in above and the key is one press away. It belongs to your workspace, which is why it cannot be issued before we know which workspace is yours.

4 · Point your client here

Each server is its own OAuth resource. A token minted for one Jithox server is refused by another, so a misconfigured client fails closed instead of spending somewhere you did not intend.

Put this in .vscode/mcp.json in your project, or open the Command Palette and run MCP: Open User Configuration to add it for every project.

EU Counterparty Sanctions Preflight — .vscode/mcp.json

{
  "servers": {
    "jithox-sanctions": {
      "type": "http",
      "url": "https://sanctions.mcp.jithox.com/mcp"
    }
  }
}

Or add it from a terminal, without editing a file:

VS Code CLI

code --add-mcp "{\"name\":\"jithox-sanctions\",\"type\":\"http\",\"url\":\"https://sanctions.mcp.jithox.com/mcp\"}"

VS Code opens a Jithox consent screen the first time it connects. Paste the access key from step 3 there once — it stays out of this file, and VS Code holds a refreshing token from then on.

There is one configuration per client above, and it is the one that works there — we checked each against this server rather than offering you a choice to make. Most clients use the consent screen, which keeps your key out of every file; Cursor sends the key on each call because its sign-in cannot return here. Either way it is the same key with the same scopes, and rotating or revoking it on this page ends access everywhere at once.

Full quickstart

5 · Check it works

This asks the server to introduce itself and list its tools. Both are free and open for discovery, so the check needs no credential and spends none of your trial. Expect 5 read-only tools.

Runs initialize and tools/list. It calls no tool, so it costs nothing and uses none of your trial.

6 · Then what

Call a tool from your own client. Every answer carries its source, the moment it was read and a signed receipt you can verify offline.

EU Counterparty Sanctions Preflight tools and examples Usage and receipts