GnistAI GnistAI
Log in

Compliance Screening

Screen entities against global sanctions lists, offshore leak databases, and corporate registries in a single API call. Instant compliance checks for KYC, AML, and due diligence workflows.

Overview   |   MCP   |   REST API   |   OpenAPI   |   CLI   |   Tutorial   |   Toolkits   |   Home
status: healthy status status healthy healthy tools: 3 tools tools 3 3 type: dataset aggregator type type dataset aggregator dataset aggregator lifecycle: maintained lifecycle lifecycle maintained maintained Legal

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

MCP Endpoint (Streamable HTTP) https://context.gnist.ai/mcp/compliance-screening/
Authentication

All requests require a Gnist-API-Key header (or api_key query parameter).

Free tier: 100 calls/day. Get 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")

ParameterTypeRequiredDescription
namestringrequiredEntity name to screen — person, company, or organization.
entity_typeanyoptionalFilter: 'individual', 'entity', or 'vessel'.
countryanyoptionalFilter by country name or code.
thresholdnumberoptionalSanctions fuzzy-match threshold (50-100). Lower = more results. (default: 80.0)
limitintegeroptionalMax results per source. (default: 10)
JSON-RPC Request
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "id": 1,
  "params": {
    "name": "screen_entity",
    "arguments": {
      "name": "123456789"
    }
  }
}
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()

JSON-RPC Request
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "id": 1,
  "params": {
    "name": "list_compliance_sources",
    "arguments": {}
  }
}
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'.

ParameterTypeRequiredDescription
feedbackstringrequired
feedback_typestringoptional (default: "general")
JSON-RPC Request
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "id": 1,
  "params": {
    "name": "report_feedback",
    "arguments": {
      "feedback": "example"
    }
  }
}

Quick Start

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

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

Related Toolkits (Legal)

Resources