CompliAPI
CompliAPI: “Real-time OFAC and global sanctions screening API: screen crypto addresses, emails, websites, government IDs, and countries against the US Treasury SDN list and 10+ sanctions, crime, and risk lists, with VPN detection and IP geolocation.”
Does the MCP server use the same API credentials?
“Yes. Authenticate with your existing CompliAPI API token as a bearer header. Tool calls are metered against your organization's quota exactly like REST requests.”
View in the company profileWhich tools does the server expose?
“screencryptoaddress, screenemail, screenwebsite, screengovernmentid, screencountry, screenpep, detectvpn and geolocateip — the full set of CompliAPI screening capabilities.”
View in the company profileWhich MCP clients are supported?
“Any client that supports remote MCP servers over streamable HTTP. Add the server URL and an Authorization header to the client's MCP configuration.”
View in the company profileIs the data different from the REST API?
“No. The MCP tools call the same screening logic and the same OFAC SDN data, refreshed every 15 minutes, as the REST endpoints.”
View in the company profileShould agents be the only place screening happens?
“For critical flows, most teams also enforce checks deterministically in application code — the REST API exposes the same data with the same credentials, so the backstop is one request away.”
View in the company profile