com.compliapi/screening
REMOTE · API.COMPLIAPI.COM
OFAC and global sanctions screening: crypto addresses, emails, websites, IDs, countries, VPN, geo
Available components
Last scanned (6 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 669 tokens (~66/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 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
- 25 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
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 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
- 23 Aug 26 0
- Schema quality: 586 → 662 ▼ functional
- First check of Schema quality: 100 functional
- New resource “screening_lists” functional
- New resource “usage_guide” functional
- 22 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 66 → 73 ▼ functional
- New tool “screen_pep” functional
- 11 Aug 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
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 5 Nov 2026 · Probed https://api.compliapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=compliapi.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 2f9ae1ab7fd93140e5dc1b36cdf8db1 |
| SANs: compliapi.com, *.compliapi.com | ||||||
| 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.compliapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| compliapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.compliapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.compliapi.com/mcp | HTTPS enforced | 301 | https://api.compliapi.com/mcp |
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 →
detect_vpn Detect VPN usage ~27
Detect whether an IP address is using a VPN.
| Name | Type | Req | Description |
|---|---|---|---|
| ip_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
geolocate_ip Geolocate an IP address ~34
Geolocate an IP address and flag whether it is in a sanctioned country.
| Name | Type | Req | Description |
|---|---|---|---|
| ip_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_country Check country sanctions ~48
Check whether a country or region carries sanctions designations (OFAC-curated today). `lists`: optional comma-separated list slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| lists | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_crypto_address Screen a crypto address ~60
Screen a crypto address on any chain (or an ENS name, e.g. vitalik.eth) across the enabled sanctions and crime lists. `lists`: optional comma-separated list slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| lists | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_email Screen an email address ~42
Screen an email address across the enabled sanctions and crime lists. `lists`: optional comma-separated list slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| lists | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_government_id Screen a government ID ~55
Screen a government-issued ID (passport, tax ID, …) across the enabled lists (fuzzy matching). `lists`: optional comma-separated list slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| government_id | string | yes | – |
| lists | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_pep Screen for politically exposed persons ~96
Screen a person's name against the OpenSanctions PEP (politically exposed persons) dataset. Returns scored candidates; `pep` is true when any candidate clears the 0.7 match threshold. `birth_date` (YYYY-MM-DD, or partial) and `country` (name or ISO code) sharpen matching.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | – | – | – |
| country | – | – | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_website Screen a website or domain ~44
Screen a website or domain across the enabled sanctions and crime lists. `lists`: optional comma-separated list slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| lists | – | – | – |
| website | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the com.compliapi/screening MCP server?
com.compliapi/screening is a hosted endpoint at https://api.compliapi.com/mcp, 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.compliapi.com
claude mcp add --transport http com-compliapi-screening 'https://api.compliapi.com/mcp'
What is the com.compliapi/screening MCP server?
com.compliapi/screening is an MCP server listed in the public MCP registry as com.compliapi/screening. OFAC and global sanctions screening: crypto addresses, emails, websites, IDs, countries, VPN, geo. This page covers its hosted endpoint (https://api.compliapi.com/mcp).
Is the com.compliapi/screening MCP server safe to use?
com.compliapi/screening scores 84 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 com.compliapi/screening MCP server expose?
com.compliapi/screening exposes 8 tools: screen_crypto_address, screen_email, screen_website, screen_government_id, screen_country, and 3 more. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.
Does the com.compliapi/screening MCP server require authentication?
No. We connected to com.compliapi/screening without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.compliapi/screening MCP server still maintained?
com.compliapi/screening is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.