_ registry / mcp http-sse · checked 2h ago

CompliAPI

https://api.compliapi.com

Registry code: 4038c2fc05370597

api record

Sanctions and financial-crime screening. Screen crypto addresses, emails, websites, and government IDs across multiple source lists — US OFAC SDN, FBI Lazarus Group addresses, Israel NBCTF seizures, the French Trésor register, Japan MOF sanctions, the EU consolidated list, the UK Sanctions List (FCDO), the Swiss SECO sanctions list, ransomwhe.re ransomware addresses, and Tornado Cash association lists (depositors/relayers, plus an opt-in withdrawal-recipient list). Every match names its list; `sanctioned` means a government sanctions list matched, `flagged` also covers crime-intelligence and…

endpoint
https://api.compliapi.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is CompliAPI live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is CompliAPI free to use?
No — it charges per call, from 0.01 USDC, quoted in its own 402 answers.
What tools does CompliAPI have?
8 tools: screen_government_id, screen_website, screen_crypto_address, screen_email, screen_country, geolocate_ip, screen_pep, detect_vpn.
Is CompliAPI safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.5%· all time 99.6%

latency
279ms

last good check

priced tools
8

of 8 tools

_ answered our checks, 90 days 584 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
security & compliance compliance & regulation
used for
  • screen a crypto address against sanctions
  • screen an email or website against crime lists
  • screen a person for pep status
  • check if an ip uses a vpn
  • check whether a country is sanctioned
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 8 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
8

distinct

settlements
17

last 2026-11-04

received on chain
0.17 USDC

no flags

_ what it can do 8 tools
8 paid 8 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • screen_government_id reads 0.01 USDC paid 2h ago

    Screen a government-issued ID (passport, tax ID, …) across the enabled lists (fuzzy matching). `lists`: optional comma-separated list slugs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "government_id"
  ],
  "properties": {
    "lists": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "government_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • screen_website reads 0.01 USDC paid 2h ago

    Screen a website or domain across the enabled sanctions and crime lists. `lists`: optional comma-separated list slugs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "website"
  ],
  "properties": {
    "lists": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "website": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • screen_crypto_address reads paid never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "lists": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "address": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • screen_email reads paid never probed

    Screen an email address across the enabled sanctions and crime lists. `lists`: optional comma-separated list slugs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string"
    },
    "lists": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • screen_country reads 0.01 USDC paid 6h ago

    Check whether a country or region carries sanctions designations (OFAC-curated today). `lists`: optional comma-separated list slugs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "lists": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "country": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • geolocate_ip reads 0.01 USDC paid 6h ago

    Geolocate an IP address and flag whether it is in a sanctioned country.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip_address"
  ],
  "properties": {
    "ip_address": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • screen_pep reads 0.05 USDC paid 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "country": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "birth_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • detect_vpn reads 0.01 USDC paid 6h ago

    Detect whether an IP address is using a VPN.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip_address"
  ],
  "properties": {
    "ip_address": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4038c2fc05370597.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4038c2fc05370597/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4038c2fc05370597/badge.svg)](https://brick.blue/agent/4038c2fc05370597?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on compliapi.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.