sanctions_entry
Pack: sanctions-screening · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/sanctions_entry for the schema, then POST the same URL with its arguments for the data.
Get the full Consolidated Screening List record for one entry by its uid (from sanctions_screen results, e.g. “SDN:12345”) or by OFAC entity number. Returns every field: all aliases, addresses, identity documents (passports, tax IDs, IMO numbers, crypto wallet addresses), sanction programs, license requirements, Federal Register notice, vessel details, and remarks.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
uid | string | no | Entry uid from sanctions_screen, e.g. “SDN:36318” or “EL:e123”. |
entity_number | string | no | OFAC/CSL entity number, e.g. “36318”. Used if uid is not given. |
Example call
Arguments
{
"uid": "SDN:36318"
}
curl
curl -X POST https://gateway.pipeworx.io/sanctions-screening/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"sanctions_entry","arguments":{"uid":"SDN:36318"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('sanctions_entry', {
"uid": "SDN:36318"
});
More examples
{
"entity_number": "36318"
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the sanctions-screening pack
{
"mcpServers": {
"sanctions-screening": {
"url": "https://gateway.pipeworx.io/sanctions-screening/mcp"
}
}
}
See Getting Started for client-specific install steps.