ofac-match
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OFACMATCH_DATA_DIR | No | Optional folder with SDN.CSV, ALT.CSV and ADD.CSV to use offline instead of downloading from OFAC. | |
| OFACMATCH_REFRESH_HOURS | No | Optional. Hours before the cached list is downloaded again. Default 24. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screen_nameA | Screens one person, company, vessel or aircraft name against the U.S. Treasury OFAC SDN sanctions list and returns potential matches with scores (0-100, 100 = identical) and an explanation of each. Give year of birth and country when known so conflicts can be flagged. |
| screen_namesA | Screens up to 100 names against the OFAC SDN list and returns, for each, the number of potential matches and the best one. Use screen_name for full details on any name that has matches. |
| get_sanctions_entryA | Returns the full published record of one OFAC SDN entry by its entry number: names, aliases, type, programs, dates of birth, addresses and remarks. Use it to review a potential match. |
| compare_namesA | Scores two names against each other with the same method used for screening, and shows the whole-name score, the name-parts score and how each part paired. Useful to understand or explain a score. |
| get_list_infoA | Reports which copy of the OFAC SDN list the server is using: number of entries, where it came from and when it was downloaded. |
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 5 tools
The five tools occupy distinct roles: single screening, batch screening, score explanation, list provenance, and entry lookup. The only near-collision is screen_name vs screen_names, but the descriptions explicitly state the plural is a bulk summary and directs agents to the singular for detail, which resolves the overlap.
All names follow a strict snake_case verb_noun pattern (screen_name, screen_names, compare_names, get_list_info, get_sanctions_entry). The singular/plural pair is a predictable and readable convention rather than a deviation.
Five tools is tightly scoped to the screening domain, with each tool earning its place: screen, batch screen, explain, list metadata, and entry retrieval. Nothing feels extraneous or missing at the surface level.
The core lifecycle — screen a name, screen many, explain a score, inspect the underlying SDN record, and verify list freshness — is fully covered with no dead ends. Minor gaps exist, such as no tool to browse or search entries by program/country without a name, but agents can work around this.