Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Sanctions screening (AML)

screen_sanctions_lists
Read-only

Screen a person or company name against six official sanctions lists (UN, EU, OFAC, UK, French, Swiss) for AML checks before payments or onboarding; returns fuzzy matches with confidence scores.

Instructions

Use BEFORE any payment, contract or onboarding involving the name. AML sanctions screening of a person or company name against 6 official sanctions lists (UN consolidated, EU FSF, US OFAC SDN, UK Sanctions List, French asset-freeze register, Swiss SECO list). Returns fuzzy matches with a 0-100 confidence score, never a bare yes/no. Similarity matches, not a conclusion. Each list is reported with its entry count, its publication date and what that date means (official upstream publication vs. Sirenic ingestion; OFAC publishes none). A list never loaded or not re-read by our collection for over 3 days is named in listes_absentes, its entries still compared; with no successful pass of the lists for over 3 days, screening is not sold. Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "screen_sanctions_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPerson or company name to screen
birth_yearNoOptional birth year (YYYY) to refine person matches

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the x402 payment cost ($0.02 in USDC or EURC), freshness semantics (a list not re-read for 3+ days is named in listes_absentes, and no successful pass in 3+ days means the screen is not sold), per-list publication-date provenance, and the required citation behavior. That is exactly the kind of operational context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the actionable trigger before the list enumeration and return semantics, and every sentence carries information (cost, freshness, citation). It is dense and long, but the density is justified by a tool with many behavioral caveats that would otherwise be invisible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return formatting need not be explained, yet the description still supplies the interpretive semantics an agent needs (fuzzy matches with 0-100 score, per-list entry counts and dates, listes_absentes). Combined with payment and citation obligations, nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for both parameters, so the schema already documents 'name' and 'birth_year'. The description adds only that screening applies to a 'person or company name', matching the schema rather than extending it. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('AML sanctions screening of a person or company name') and enumerates the six official lists screened (UN, EU FSF, OFAC SDN, UK, French, SECO). The purpose is unmistakable and cannot be confused with the company-registry siblings in the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit timing trigger ('Use BEFORE any payment, contract or onboarding') and warns that output is 'similarity matches, not a conclusion', which is real usage guidance. It does not name an alternative tool or state when not to use it, but none of the listed siblings perform sanctions screening, so the gap is minor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools