OFAC sanctions screen (x402)
Screen a name or crypto address against OFAC sanctions in one paid call
Answered our latest tool-list check yesterday with 1 tools. It will be marked verified after 3 successful checks in 7 days.
OFAC sanctions screen (x402) is a paid MCP server for fraud detection. It runs as a hosted remote server, so there is nothing to install locally.
- Pricing
- Paid
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add --transport http sanctions-check 'https://feeds.agentexchange.work/mcp?tools=sanctions_check'Add to Settings → Connectors → Add custom connector
https://feeds.agentexchange.work/mcp?tools=sanctions_checkAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"sanctions-check": {
"url": "https://feeds.agentexchange.work/mcp?tools=sanctions_check"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"sanctions-check": {
"type": "http",
"url": "https://feeds.agentexchange.work/mcp?tools=sanctions_check"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"sanctions-check": {
"serverUrl": "https://feeds.agentexchange.work/mcp?tools=sanctions_check"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://feeds.agentexchange.work/mcp?tools=sanctions_checkEnter a Name (for example "OFAC sanctions screen (x402)"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"sanctions-check": {
"type": "http",
"url": "https://feeds.agentexchange.work/mcp?tools=sanctions_check"
}
}
}Using several servers? Build one config file with the MCP config generator.
About OFAC sanctions screen (x402)
This server checks a name or a crypto address against OFAC sanctions in a single call. It is one of the paid routes from Agent Exchange feeds, billed at $0.002 per call over x402 or MPP in USDC on Base, with no account or API key.
Unpaid requests receive an HTTP 402 response with both payment challenges, so an agent with a wallet can pay and retry automatically.
The same host offers other pay-per-call feeds such as US Federal Register notices, SEC EDGAR filings and Base token data, each exposed as its own small tool.
Tools this server provides (1)
Read directly from the server.
All 1 tool say they're read-only.
From the server's own tool annotations; not verified by us.
- sanctions_checkSays read-only
- OFAC sanctions screen in one call against the US Treasury SDN list: by name (also matches aliases) or by crypto address (SDN-listed digital currency addresses): matches with entity number, type, program, remarks (name=Acme Trading or address=0x...). Screening aid, not a compliance determination. Pay per call $0.002 USDC on Base via x402.
What it does
- Name screening
- Checks a person or company name against OFAC sanctions.
- Crypto address screening
- Checks a crypto address in the same call.
- Micropayments
- $0.002 per call over x402 or MPP in USDC on Base.
- No account or key
- Payment happens in the call itself.
- 402 challenge flow
- Unpaid requests get an HTTP 402 with payment challenges.
Good for
- Screen a counterparty name before a payment
- Check a wallet address before sending funds
- Add a sanctions check to a compliance agent
- Run occasional screens without a vendor contract
Pricing
Paid
$0.002 per call in USDC on Base
Prices change. Check feeds.agentexchange.work before you buy.
OFAC sanctions screen (x402) FAQ
How much does a check cost?
$0.002 per call.
What can I screen?
A name or a crypto address.
How do I pay?
With USDC on Base through x402 or MPP, without an account.
How do I add OFAC sanctions screen (x402) to Claude Code?
Run this command in your terminal: claude mcp add --transport http sanctions-check 'https://feeds.agentexchange.work/mcp?tools=sanctions_check'
What are the best alternatives to OFAC sanctions screen (x402)?
The closest alternatives to OFAC sanctions screen (x402) are PayGuard, Sanctions Screen (OFAC, UN, EU, UK), Sanctions Screen (OFAC, EU, UK, UN), EdgeScreen x402 Security Screening and Sanctions Screening.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Status and tools: checked automatically by AIPoweredBot on 21 November 2026.
- Install steps: from the official MCP Registry entry.