fairquery-sanctions-screener
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | No | Optional Apify API token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screen_namesA | Fuzzy-match people or company names against OFAC SDN + Consolidated, EU, UK and UN sanctions lists downloaded fresh from the official sources. One row per name: status potential_match/no_match, best_score (0-100), matches with list, entry id, primary name, aliases, programs, countries, DOB, country_match/dob_match. Optional per-name country and dateOfBirth filters. Runs Apify Actor fairquery/sanctions-watchlist-screener; requires APIFY_TOKEN, billed per name. Not a certified screening service. Automated fuzzy matching against public lists downloaded at run time; results can contain false positives and miss matches. Review every potential match manually and consult official sources and legal counsel before acting. |
| list_sourcesA | Free, local, no token: the official lists screen_names checks (id, name, authority, download URL), the score scale and the disclaimer. Use it to pick the lists parameter or to cite sources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve clearly different purposes: list_sources is a metadata/discovery call (available lists, scoring scale, disclaimer), while screen_names performs the actual fuzzy-match screening. There is no overlap or risk of misselection.
Both names follow a consistent verb_noun snake_case pattern (list_sources, screen_names). The convention is predictable and readable.
Two tools is minimal for the stated purpose; it covers discovery plus screening but leaves no room for per-entry detail or batch/export operations. It is borderline thin rather than clearly right-sized.
Core workflow is covered: discover authoritative sources and screen names with detailed per-match output (scores, programs, countries, DOB). Minor gaps exist, such as retrieving a single list entry or exporting/batch-result retrieval, but agents can work around them.