Skip to content

Compliance Engine

by Alex-Dev-Web-C-DE · remote · no sign-in to list tools · v1.0.0 · published by GitHub user Alex-Dev-Web-C-DE

Sanctions screening (OFAC/UK/EU/UN) + PEP + GLEIF entities via Compliance Engine.

Changes · 2
CompareRegistry entry

3 tools: 2 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http compliance-engine https://compliance-engine-mcp.mcpize.run/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 2Claude Code: ask
  • check_pepCheck if a person is a Politically Exposed Person (PEP).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check if a person is a Politically Exposed Person (PEP). 11.7K+ PEP records from Wikidata.
  • check_sanctionsScreen a person or entity against global sanctions lists (OFAC SDN, UK OFSI, EU Consolidated, UN Consolidated).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Screen a person or entity against global sanctions lists (OFAC SDN, UK OFSI, EU Consolidated, UN Consolidated). Returns matches with confidence scores.
Only reads 1Claude Code: allow
  • check_entitySearch legal entities by name in GLEIF database (20K+ records).No findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.
    Description, as the server wrote it
    Search legal entities by name in GLEIF database (20K+ records). Returns LEI, legal name, jurisdiction.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http compliance-engine https://compliance-engine-mcp.mcpize.run/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__compliance-engine__check_entity"
    ],
    "ask": [
      "mcp__compliance-engine__check_sanctions",
      "mcp__compliance-engine__check_pep"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as compliance-engine. Review it before you use it.