Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Compliance & Sanções

REMOTE · API.MCP.AI · SCANNED OCT 6

Due diligence & KYC: PEP, national and international sanctions (OFAC, UN, EU, UK, FBI, INTERPOL, FIN

Available components

+1 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Compliance & Sanções MCP server?

Compliance & Sanções is a hosted endpoint at https://api.mcp.ai/p_compliance, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-compliance-mcp 'https://api.mcp.ai/p_compliance'
// .cursor/mcp.json
{
  "mcpServers": {
    "mcp-dir-compliance-mcp": {
      "url": "https://api.mcp.ai/p_compliance"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mcp-dir-compliance-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_compliance"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.mcp-dir-compliance-mcp]
url = "https://api.mcp.ai/p_compliance"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-compliance-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_compliance",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mcp-dir-compliance-mcp --url 'https://api.mcp.ai/p_compliance' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mcp-dir-compliance-mcp:
    url: "https://api.mcp.ai/p_compliance"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mcp-dir-compliance-mcp": {
      "Transport": "http",
      "Url": "https://api.mcp.ai/p_compliance"
    }
  }
}
# add to Vellum
assistant mcp add mcp-dir-compliance-mcp -t streamable-http -u 'https://api.mcp.ai/p_compliance'
// mcp.json
{
  "mcpServers": {
    "mcp-dir-compliance-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_compliance"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HTTPS: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 4 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.356 → 0.9.358 functional
  • 3 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.353 → 0.9.356 functional
  • 1 Oct 26 +1
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.351 → 0.9.353 functional
  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Oct 2026 · Probed https://api.mcp.ai/p_compliance

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 1bf4d405299e078a0e62ff16cded599b
SANs: mcp.ai, *.mcp.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.mcp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
mcp.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mcp.ai/p_compliance Unreachable
http (plaintext) http://api.mcp.ai/p_compliance HTTPS enforced
MCP tools · 37 exposed · ~2,307 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
authenticate ~99

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

compliance_antecedentes_civil ~93

Antecedentes criminais (Polícia Civil) por CPF/nome/UF.

NameTypeReqDescription
CPFstring––
DATANASCIMENTOstring––
GENEROstring––
NOMEstring––
NOMEMAEstring––
RGstring––
UFstringyes–
completoboolean––

No output schema declared.

No examples provided.

compliance_antecedentes_pf ~78

Antecedentes criminais (Polícia Federal) por CPF/nome.

NameTypeReqDescription
CPFstring––
DATANASCIMENTOstring––
NOMEstring––
NOMEMAEstring––
NOMEPAIstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_antt ~57

Regularidade de transportadora na ANTT por CPF/CNPJ/RNTRC.

NameTypeReqDescription
CNPJstring––
CPFstring––
RNTRCstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_bacen_inabilitados ~41

Banco Central — quadro geral de inabilitados, por CPF/CNPJ.

NameTypeReqDescription
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_bacen_proibidos ~48

Banco Central — quadro geral de proibidos, por CPF/CNPJ.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_cadin ~56

CADIN estadual (inadimplentes com a Fazenda) por CPF/CNPJ/UF.

NameTypeReqDescription
CNPJstring––
CPFstring––
UFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_carf ~52

Processos no CARF (Conselho Administrativo de Recursos Fiscais) por CPF/CNPJ.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_ceaf ~35

CEAF — expulsões da administração federal, por CPF.

NameTypeReqDescription
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_ceis ~49

CEIS — empresas inidôneas e suspensas, por CNPJ/CPF.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_cepim ~37

CEPIM — entidades privadas impedidas, por CNPJ.

NameTypeReqDescription
CNPJstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_cgu ~50

Consulta de penalidades CGU por CPF/CNPJ.

NameTypeReqDescription
CNPJstring––
CPFstring––
TIPOstringyes–
completoboolean––

No output schema declared.

No examples provided.

compliance_cnd_municipal ~69

Certidão Negativa de Débitos Municipal por CNPJ/CPF (informe o município).

NameTypeReqDescription
CNPJstring––
CPFstring––
IMstring––
MUNICIPIOstringyes–
completoboolean––

No output schema declared.

No examples provided.

compliance_cnep ~46

CNEP — empresas punidas, por CNPJ/CPF.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_confea_crea ~51

Registro profissional no CONFEA/CREA (engenharia/agronomia).

NameTypeReqDescription
CPFstring––
REGISTRONACIONALstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_cvm ~49

Cadastro na CVM (Comissão de Valores Mobiliários) por CPF/CNPJ.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_cvm_sancionadores ~49

Processos administrativos sancionadores da CVM por CPF/CNPJ.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_fbi ~33

Busca na lista FBI Most Wanted por nome.

NameTypeReqDescription
NOMEstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_fincen ~34

Busca na lista FINCEN por nome.

NameTypeReqDescription
NOMEstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_ibama_debitos ~47

Certidão negativa de débitos do IBAMA por CPF/CNPJ.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_improbidade ~52

CNIA — condenações por improbidade administrativa e inelegibilidade, por CNPJ/CPF.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_interpol ~52

Busca na lista da INTERPOL por nome.

NameTypeReqDescription
DATANASCIMENTOstring––
NOMEstring––
SOBRENOMEstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_leniencia ~34

Acordos de leniência por CNPJ.

NameTypeReqDescription
CNPJstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_mandados_prisao ~79

CNJ — mandados de prisão em aberto, por CPF/nome.

NameTypeReqDescription
ALCUNHAstring––
CPFstring––
NOMEstring––
NOMEMAEstring––
NOMEPAIstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_ofac ~39

Busca em listas de sanções OFAC (EUA) por nome.

NameTypeReqDescription
NOMEstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_onu ~37

Busca na lista consolidada de sanções da ONU por nome.

NameTypeReqDescription
NOMEstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_pep ~38

Verifica se um CPF é Pessoa Exposta Politicamente (PEP).

NameTypeReqDescription
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_pep_parentescos ~40

PEP estendida — pessoa exposta politicamente + parentescos.

NameTypeReqDescription
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_pix ~54

Antifraude de chave PIX — valida o titular de uma chave PIX.

NameTypeReqDescription
CHAVEstringyes–
DOCUMENTOstringyes–
TIPOstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_trabalho_forcado ~54

Verificação de empregador em lista de trabalho forçado/escravo, por CNPJ/CPF.

NameTypeReqDescription
CNPJstring––
CPFstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_ue ~37

Busca na lista de sanções financeiras da União Europeia por nome.

NameTypeReqDescription
NOMEstring––
completoboolean––

No output schema declared.

No examples provided.

compliance_uk ~40

Busca na lista de sanções do Reino Unido (HM Treasury) por nome.

NameTypeReqDescription
NOMEstring––
completoboolean––

No output schema declared.

No examples provided.

connect ~42

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

marketplace ~532

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

NameTypeReqDescription
actionstring––
argumentsstring––
cancel_commentstring––
cancel_reasonstring––
conversationstring––
immediateboolean––
limitnumber––
mcp_idstring––
messagestring––
prompt_bodystring––
prompt_categorystring––
prompt_descriptionstring––
prompt_slugstring––
prompt_targetsarray––
prompt_titlestring––
prompt_toolstring––
prompt_varsstring––
querystring––
report_contextstring––
request_detailsstring––
request_namestring––
tier_slugstring––
tool_idstring––

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring––
conversationstring––
messagestringyes–

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~37

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Compliance & Sanções MCP server?

Compliance & Sanções is an MCP server listed in the public MCP registry as io.github.mcp-dir/compliance-mcp. Due diligence & KYC: PEP, national and international sanctions (OFAC, UN, EU, UK, FBI, INTERPOL, FIN. This page covers its hosted endpoint (https://api.mcp.ai/p_compliance).

Is the Compliance & Sanções MCP server safe to use?

Compliance & Sanções scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Compliance & Sanções MCP server expose?

Compliance & Sanções exposes 37 tools: compliance_pep, compliance_pep_parentescos, compliance_ofac, compliance_onu, compliance_ue, and 32 more. Their descriptions and schemas cost roughly 2,307 tokens of context every time the server is loaded.

Does the Compliance & Sanções MCP server require authentication?

Its publisher declares no required credentials for Compliance & Sanções. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Compliance & Sanções MCP server still maintained?

Compliance & Sanções is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.