OFACScreen Sanctions Screening

Sanctions screening (OFAC SDN + 13 more lists)

screen_entity

Read-onlyIdempotent

Screen a person or company name against 14 sanctions and export-control lists: OFAC SDN, OFAC Non-SDN, EU Financial Sanctions, UN Security Council, UK Sanctions List, Canada SEMA, Swiss SECO, Australia DFAT, BIS Denied Persons, BIS Entity List, BIS Unverified List, BIS Military End-User, ITAR Debarred and State Nonproliferation. Fuzzy name matching, so transliterations and spelling variants still surface. Returns the number of potential matches and the ten highest scoring, each with its score, list, program, aliases and addresses. A score is name similarity, not a finding that a match is the same party: confirm a date of birth, an address or an ID document before acting on it. Free, no account, 25 screenings a day from each internet address, shared by screen_entity and screen_address; in ChatGPT, each user has their own 25. A screening is not recorded and produces no document: its report_url opens the same search on ofacscreen.com, where a timestamped PDF record of it can be bought. The price is in report_price. Calling this tool is free. Searched only when named in lists: UAE Local Terrorist List, UFLPA Entity List, FBI Most Wanted, FinCEN Special Measures, France Registre des gels, Israel NBCTF crypto wallets, Japan MOF, Mexico SAT 69-B, Poland MSWiA.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Full name of the person or entity to screen, e.g. "Vladimir Petrov" or "Acme Trading LLC". Up to 300 characters.
`email`	No	The party's email address, checked against the ones the lists record. Optional; up to 5 separated by commas or semicolons.
`lists`	No	List codes to search instead of the default 14. Omit to search the default lists.
`phone`	No	The party's phone number, checked against the ones the lists record. Optional; up to 5 separated by commas or semicolons.
`website`	No	The party's website, checked against the ones the lists record. Optional; up to 5 separated by commas or semicolons.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`results`	Yes
`contacts`	No
`report_url`	Yes
`match_found`	Yes
`screened_at`	No
`report_price`	Yes
`results_count`	Yes
`results_shown`	No
`lists_screened`	No
`contact_matches`	No
`is_audit_record`	No
`lists_refreshed`	No
`results_truncated`	No
`results_count_is_capped`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 19, 2026

addedInput schema / properties / email

Added value: +{
+  "description": "The party's email address, checked against the ones the lists record. Optional; up to 5 separated by commas or semicolons.",
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / phone

Added value: +{
+  "description": "The party's phone number, checked against the ones the lists record. Optional; up to 5 separated by commas or semicolons.",
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / website

Added value: +{
+  "description": "The party's website, checked against the ones the lists record. Optional; up to 5 separated by commas or semicolons.",
+  "maxLength": 300,
+  "type": "string"
+}

addedOutput schema / properties / contact_matches

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / contacts

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / lists / items / enum

Previous value: -[
-  "AE_EOCN",
-  "AU_DFAT",
-  "BIS_DPL",
-  "BIS_EL",
-  "BIS_MEU",
-  "BIS_UVL",
-  "CANADA_SEMA",
-  "EU_FSF",
-  "FBI_WANTED",
-  "FR_GELS",
-  "JP_MOF",
-  "MX_SAT_69B",
-  "OFAC_NONSDN",
-  "OFAC_SDN",
-  "PL_MSWIA",
-  "STATE_DTC",
-  "STATE_ISN",
-  "SWISS_SECO",
-  "UK_SANCTIONS",
-  "UN_CONSOLIDATED"
-]New value: +[
+  "AE_EOCN",
+  "AU_DFAT",
+  "BIS_DPL",
+  "BIS_EL",
+  "BIS_MEU",
+  "BIS_UVL",
+  "CANADA_SEMA",
+  "DHS_UFLPA",
+  "EU_FSF",
+  "FBI_WANTED",
+  "FINCEN_311",
+  "FR_GELS",
+  "IL_NBCTF",
+  "JP_MOF",
+  "MX_SAT_69B",
+  "OFAC_NONSDN",
+  "OFAC_SDN",
+  "PL_MSWIA",
+  "STATE_DTC",
+  "STATE_ISN",
+  "SWISS_SECO",
+  "UK_SANCTIONS",
+  "UN_CONSOLIDATED"
+]

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / lists / items / enum

Previous value: -[
-  "AU_DFAT",
-  "BIS_DPL",
-  "BIS_EL",
-  "BIS_MEU",
-  "BIS_UVL",
-  "CANADA_SEMA",
-  "EU_FSF",
-  "FBI_WANTED",
-  "JP_MOF",
-  "MX_SAT_69B",
-  "OFAC_NONSDN",
-  "OFAC_SDN",
-  "STATE_DTC",
-  "STATE_ISN",
-  "SWISS_SECO",
-  "UK_SANCTIONS",
-  "UN_CONSOLIDATED"
-]New value: +[
+  "AE_EOCN",
+  "AU_DFAT",
+  "BIS_DPL",
+  "BIS_EL",
+  "BIS_MEU",
+  "BIS_UVL",
+  "CANADA_SEMA",
+  "EU_FSF",
+  "FBI_WANTED",
+  "FR_GELS",
+  "JP_MOF",
+  "MX_SAT_69B",
+  "OFAC_NONSDN",
+  "OFAC_SDN",
+  "PL_MSWIA",
+  "STATE_DTC",
+  "STATE_ISN",
+  "SWISS_SECO",
+  "UK_SANCTIONS",
+  "UN_CONSOLIDATED"
+]

Changed1 schema field changedOct 13, 2026

addedInput schema / properties / lists

Added value: +{
+  "description": "List codes to search instead of the default 14. Omit to search the default lists.",
+  "items": {
+    "enum": [
+      "AU_DFAT",
+      "BIS_DPL",
+      "BIS_EL",
+      "BIS_MEU",
+      "BIS_UVL",
+      "CANADA_SEMA",
+      "EU_FSF",
+      "FBI_WANTED",
+      "JP_MOF",
+      "MX_SAT_69B",
+      "OFAC_NONSDN",
+      "OFAC_SDN",
+      "STATE_DTC",
+      "STATE_ISN",
+      "SWISS_SECO",
+      "UK_SANCTIONS",
+      "UN_CONSOLIDATED"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 12, 2026
- addedOutput schema / properties / results / items / properties / matched_identifier
```
Added value: +{
+  "type": "boolean"
+}
```

Changed13 schema fields changedAug 19, 2026

removedInput schema / properties / entity_type

Removed value: -{
-  "description": "Optional filter: restrict matches to individuals or to entities/organizations. Omit to search both.",
-  "enum": [
-    "individual",
-    "entity"
-  ],
-  "type": "string"
-}

changedInput schema / properties / name / description

Previous value: -"Full name of the person or entity to screen, e.g. \"Vladimir Petrov\" or \"Acme Trading LLC\"."New value: +"Full name of the person or entity to screen, e.g. \"Vladimir Petrov\" or \"Acme Trading LLC\". Up to 300 characters."

addedInput schema / properties / name / maxLength
```
Added value: +300
```
addedOutput schema / properties / is_audit_record
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / lists_refreshed

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / lists_screened
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / results / items / properties / addresses_total
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / results / items / properties / aliases_total
```
Added value: +{
+  "type": "integer"
+}
```
changedOutput schema / properties / results / items / properties / matched_alias / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / results_count_is_capped
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / results_shown
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / results_truncated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / screened_at
```
Added value: +{
+  "type": "string"
+}
```

First observedAug 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes far beyond the readOnly/idempotent annotations: discloses fuzzy matching behavior, the exact result shape (count plus top ten with score, list, program, aliases, addresses), the crucial caveat that a score is name similarity not a party match, that nothing is recorded, and that report_url is an upsell with a price. No contradiction with annotations.

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

Conciseness3/5

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

The core purpose and the match-score caveat are front-loaded, which is good, but the block is long and repeats the free-of-charge message ('Free, no account, 25 screenings a day…' followed later by 'Calling this tool is free.') and splits the report_url/report_price explanation across two sentences that could be one.

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?

For a screening tool with an output schema already defining return values, the description still covers cost, quota, non-recording, match-scoring caveats and list defaults. Nothing an agent needs to call this safely and correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning the schema cannot: it names which 14 lists are the default for the omitted lists parameter and explains that nine further lists (UAE, UFLPA, FBI, FinCEN, France, Israel, Japan, Mexico, Poland) are only searched when explicitly named in the enum.

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?

Specific verb ('screen') plus resource ('a person or company name') and an enumerated set of 14 named lists, so the agent knows exactly what is queried. The name-vs-address distinction against the sibling screen_address is implicit in the wording 'person or company name' but the tool is still unambiguously identifiable.

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?

States the operating envelope clearly: free, no account, 25 screenings/day per IP, shared between screen_entity and screen_address, and per-user quota in ChatGPT. It does not explicitly say 'use screen_address for addresses instead' nor point to list_sanctions_sources for discovering list codes, so routing guidance is strong but not complete.

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

All OFACScreen Sanctions Screening tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?