Tutorial: Compliance Screening

Legal

Data source: OFAC, EU, UN, UK OFSI, ICIJ Offshore Leaks, GLEIF

Overview

Compliance Screening searches across 6 data sources (OFAC, EU, UN, UK OFSI, ICIJ Offshore Leaks, GLEIF) in a single query. It deduplicates and normalizes results, saving you from building 6 separate integrations. This tutorial walks through all 3 tools with working code examples.

Prerequisites

Sign up at https://context.gnist.ai/signup for a free API key (100 calls/day).
Choose your integration method: MCP protocol or REST API.

Connect via MCP

Add to your MCP client config (Claude Desktop, Cursor, etc.):

MCP Config

{
  "mcpServers": {
    "gnist-compliance-screening": {
      "url": "https://context.gnist.ai/mcp/compliance-screening/",
      "headers": {
        "Gnist-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Tools (3)

`screen_entity`

Screen an entity for sanctions, offshore leaks, and corporate registry hits. Queries OFAC/EU/UN/UK sanctions lists, ICIJ Offshore Leaks (Panama/Paradise/Pandora Papers), and GLEIF corporate registry in parallel. Returns a unified risk assessment. The risk_level field summarizes the findings: - clear: no matches found in any database - low: minor signals only - medium: possible matches requiring review - high: probable matches in sanctions or offshore leaks - critical: high-confidence sanctions match Examples: screen_entity(name="Gazprom") screen_entity(name="Kim Jong Un", entity_type="individual") screen_entity(name="Evrofinance Mosnarbank", country="Russia")

Parameter	Type	Required	Description
`name`	string	required	Entity name to screen — person, company, or organization.
`entity_type`	any	optional	Filter: 'individual', 'entity', or 'vessel'.
`country`	any	optional	Filter by country name or code.
`threshold`	number	optional	Sanctions fuzzy-match threshold (50-100). Lower = more results. (default: `80.0`)
`limit`	integer	optional	Max results per source. (default: `10`)

curl -X POST "https://context.gnist.ai/mcp/compliance-screening/" \
  -H "Content-Type: application/json" \
  -H "Gnist-API-Key: YOUR_API_KEY" \
  -d '{"jsonrpc": "2.0", "method": "tools/call", "id": 1, "params": {"name": "screen_entity", "arguments": {"name": "example"}}}'

import httpx

resp = httpx.post(
    "https://context.gnist.ai/mcp/compliance-screening/",
    headers={"Gnist-API-Key": "YOUR_API_KEY"},
    json={'id': 1,
 'jsonrpc': '2.0',
 'method': 'tools/call',
 'params': {'arguments': {'name': 'example'}, 'name': 'screen_entity'}},
)
print(resp.json())

`list_compliance_sources`

List all compliance data sources, their coverage, and data types. Shows which sanctions lists, leak databases, and corporate registries are searched during screening. Examples: list_compliance_sources()

curl -X POST "https://context.gnist.ai/mcp/compliance-screening/" \
  -H "Content-Type: application/json" \
  -H "Gnist-API-Key: YOUR_API_KEY" \
  -d '{"jsonrpc": "2.0", "method": "tools/call", "id": 1, "params": {"name": "list_compliance_sources", "arguments": {}}}'

import httpx

resp = httpx.post(
    "https://context.gnist.ai/mcp/compliance-screening/",
    headers={"Gnist-API-Key": "YOUR_API_KEY"},
    json={'id': 1,
 'jsonrpc': '2.0',
 'method': 'tools/call',
 'params': {'arguments': {}, 'name': 'list_compliance_sources'}},
)
print(resp.json())

`report_feedback`

Report a bug, feature request, or general feedback for this data source. Use this when something doesn't work as expected, when you'd like a new feature, or when you have suggestions for improvement. Args: feedback: Describe the issue or suggestion. feedback_type: One of 'bug', 'feature_request', or 'general'.

Parameter	Type	Required	Description
`feedback`	string	required
`feedback_type`	string	optional	(default: `general`)

curl -X POST "https://context.gnist.ai/mcp/compliance-screening/" \
  -H "Content-Type: application/json" \
  -H "Gnist-API-Key: YOUR_API_KEY" \
  -d '{"jsonrpc": "2.0", "method": "tools/call", "id": 1, "params": {"name": "report_feedback", "arguments": {"feedback": "example"}}}'

import httpx

resp = httpx.post(
    "https://context.gnist.ai/mcp/compliance-screening/",
    headers={"Gnist-API-Key": "YOUR_API_KEY"},
    json={'id': 1,
 'jsonrpc': '2.0',
 'method': 'tools/call',
 'params': {'arguments': {'feedback': 'example'}, 'name': 'report_feedback'}},
)
print(resp.json())

Common Patterns

Pagination
Several tools support limit, offset, or page parameters. Start with small limits during development, then increase for production queries.

FAQ

What data does Compliance Screening provide?

Unified entity due diligence across OFAC/EU/UN/UK sanctions, ICIJ offshore leaks, and GLEIF corporate registry — parallel screening with risk assessment. It exposes 3 tools: screen_entity, list_compliance_sources, report_feedback.

What do I need to get started?

A Gnist API key (free tier: 100 calls/day). Sign up at https://context.gnist.ai/signup.

What format does the Compliance Screening API return?

JSON, via either MCP protocol (JSON-RPC 2.0) or REST API.

Which data sources does Compliance Screening aggregate?

OFAC, EU, UN, UK OFSI, ICIJ Offshore Leaks, GLEIF. Results are deduplicated and normalized into a consistent format.