A powerful sanctions screening API MCP Server, leveraging OFAC API to provide comprehensive risk assessments for individuals and organizations.
🎉 Ready for integration with Claude through the Model Context Protocol 🎉
Screen.Recording.2025-04-23.at.11.06.13.PM.movYou can run the Sanctions MCP Server using Node.js directly.
git clone https://github.com/yourusername/mcp-ofac cd mcp-ofac3. Configure
claude_desktop_config.json
Add the following configuration to your claude_desktop_config.json
file. Make sure to:
{ "mcpServers": { "sanctions": { "command": "/path/to/your/node", "args": ["/path/to/your/mcp-ofac/index.js"], "env": { "OFAC_API_API_KEY": "YOUR_API_KEY_HERE" } } } }
You can ask Claude to screen individuals against sanctions lists:
"Can you check if John Smith born on 1980-01-15 from Syria is on any sanctions lists?"
Screening an OrganizationYou can ask Claude to check organizations:
"Is there a sanctioned entity called Tech Solutions Ltd based in Tehran, Iran?"
Custom Screening ParametersYou can specify custom parameters for more targeted screening:
"Check if Maria Rodriguez with passport number AB123456 from Venezuela is on the OFAC SDN list with a minimum match score of 90."
The Sanctions MCP Server processes screening requests with the following parameters:
The tool returns detailed match information, including sanctioned entity details, match scores, and source information.
The server accepts detailed entity information including:
The server returns a JSON response with:
After configuring your claude_desktop_config.json
, restart Claude Desktop to apply the changes and enable the sanctions screening capability.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4