Skip to main content
Glama

Server Details

Screen names and crypto wallets against OFAC, UK, EU and UN sanctions lists, with list dates

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Bosco-Labs/bosco-labs-data
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 3 tools

Disambiguation4/5

The planner tool is clearly a different kind of operation (plan generation vs. actual screening), and sanctions_screening is explicitly scoped to sanctions lists plus crypto addresses. The one confusion point is counterparty_check vs. sanctions_screening, since both screen entities against 'official sources' and an agent asking 'is this party sanctioned?' could plausibly pick either, but the descriptions (KYB checklist vs. sanctions lists with per-list attribution) mostly resolve it.

Naming Consistency4/5

All three names are snake_case and readable, with a predictable resource-oriented style (counterparty_check, sanctions_screening). The minor deviation is plan_official_records_query, which is verb-led while the other two are noun phrases, and none of the names embed the parameter style used elsewhere.

Tool Count3/5

Three tools is thin for a compliance/screening surface, especially since two of them overlap on name screening. It also appears to be an incomplete slice of a larger ecosystem, as the planner references run_official_records_plan, which is not part of this server.

Completeness3/5

Core screening workflows are covered (single/batch name screening, wallet address checks, sourced results, free query planning), but the planner's advertised execution path (run_official_records_plan) is absent, leaving a dead end unless the agent calls listed tools directly. There is also no result retrieval, monitoring/re-screening, or report/audit export operation.

Available Tools

3 tools
counterparty_checkCounterparty Check API: KYB checklist from official registersA
Read-onlyIdempotent
Inspect

Can I do business with this company? One call checks a supplier, customer or partner against official sources and returns a checklist: pass, fail, review or unverified per check, each with its source link and time. Built for AI agents doing KYB, vendor onboarding or "may I pay this party?" checks, and for people who want a fast, sourced first screen. To screen a vendor list, pass up to 10 companies in companies: one checklist per company, same price each.

Price: $0.05 per counterparty-check.

NameRequiredDescriptionDefault
ibanNoThe bank account the counterparty wants to be paid on, e.g. "DK5000400440116243"
queryNoThe counterparty to check: a name (e.g. "Novo Nordisk") or an identifier: LEI
countryNoISO 3166 alpha-2 country code to disambiguate, e.g. "DK", "GB", "NO", "FR", "FI", "EE", "IE", "CZ", "LV", "NL", "US"
companiesNoCheck a list of companies in one run instead of `query`: up to 10 companies, each a name or number ("Tesco PLC") or an object with the fields above
vatNumberNoThe VAT number the counterparty gave you, with its country prefix, e.g. "DK24256790"
walletAddressesNoWallet addresses the counterparty wants to be paid on, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]
plan_official_records_queryPlan an official-records queryA
Read-onlyIdempotent
Inspect

Free, no key needed. Turns a question in plain words into the exact typed Bosco Labs calls that answer it: tool, input, why, and the maximum price of each step, plus what is not covered. Pass the user's question verbatim AND the entities you extracted from it (company_names, tickers, identifiers, countries, dates, law references...): the planner trusts your entities over its own parsing and puts them in the right input fields. The plan echoes them in entities_used and lists in missing what to pass for a better plan. Rules and examples first; only when they are unsure and you passed no entities does a small AI step extract the entities (budget-capped, marked assisted). Same steps, same plan_id. Run it with run_official_records_plan (paid, max_usd) or call the listed tools directly. Low confidence returns the top 3 candidate tools instead.

NameRequiredDescriptionDefault
entitiesNoWhat you (the calling agent) already extracted from the user's question. Extract these from the question yourself; the planner trusts them over its own parsing and puts them in the right input fields. The plan echoes them in `entities_used` and names what is still missing in `missing`, so you can re-call with more.
questionYesThe user's question, verbatim, e.g. "Is Rosneft on the EU sanctions list?" (English, Dutch, German or French).
sanctions_screeningSanctions List Screening API: OFAC, UK, EU, UN & US listsA
Read-onlyIdempotent
Inspect

Answers "is this company, vessel or person sanctioned?" for one or many names, against the official OFAC SDN and non-SDN lists, the US Consolidated Screening List (Commerce Entity List, Denied Persons, State lists), the UK Sanctions List, the EU financial sanctions list and the UN Security Council list. Every answer says which lists were checked and how current they were, and every match links to its official source. Built for AI agents doing KYB, compliance or procurement checks, and for people who need a quick, sourced screen. It also checks crypto wallet addresses exactly against the addresses OFAC lists (XBT, ETH, USDT, TRX and more), e.g. before an agent pays.

Price: $0.01 per name-screened.

NameRequiredDescriptionDefault
listsNoWhich lists to check, any of "ofac_sdn", "ofac_consolidated", "us_csl", "uk", "eu", "un", e.g. ["ofac_sdn", "uk"]
namesNoCompany, vessel or person names to check, one per entry, as plain text, e.g. ["Sovcomflot", "Novo Nordisk A/S"]
countryNoCountry of the party you are screening, as an ISO 3166 alpha-2 code or English name, e.g. "RU" or "Russia"
minScoreNoLowest similarity score (0-100) that counts as a match, e.g. 85 (default)
addressesNoCrypto wallet addresses to check, one per entry, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]
entityTypeNoOnly return listings of this type, e.g. "organization"any

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcounterparty_check1 field changed
      • changedInput schema / properties / country / description
        Previous value: -"ISO 3166 alpha-2 country code to disambiguate, e.g. \"DK\", \"GB\", \"NO\", \"FR\", \"FI\", \"EE\", \"NL\", \"US\""New value: +"ISO 3166 alpha-2 country code to disambiguate, e.g. \"DK\", \"GB\", \"NO\", \"FR\", \"FI\", \"EE\", \"IE\", \"CZ\", \"LV\", \"NL\", \"US\""
  2. 1 tool update
    • Changedcounterparty_check5 fields changed
      • changedInput schema / properties / companies / description
        Previous value: -"Check a list of companies in one run instead of `query`: up to 10 objects with the fields above"New value: +"Check a list of companies in one run instead of `query`: up to 10 companies, each a name or number (\"Tesco PLC\") or an object with the fields above"
      • addedInput schema / properties / companies / items / anyOf
        Added value: +[
        +  {
        +    "type": "string"
        +  },
        +  {
        +    "properties": {
        +      "country": {
        +        "description": "ISO 3166 alpha-2 code, e.g. \"DK\"",
        +        "type": "string"
        +      },
        +      "iban": {
        +        "description": "As in `iban`, e.g. \"DK5000400440116243\"",
        +        "type": "string"
        +      },
        +      "query": {
        +        "description": "Name, LEI or registration number, as in `query`, e.g. \"24256790\"",
        +        "type": "string"
        +      },
        +      "vatNumber": {
        +        "description": "As in `vatNumber`, e.g. \"DK24256790\"",
        +        "type": "string"
        +      }
        +    },
        +    "required": [
        +      "query"
        +    ],
        +    "type": "object"
        +  }
        +]
      • removedInput schema / properties / companies / items / properties
        Removed value: -{
        -  "country": {
        -    "description": "ISO 3166 alpha-2 code, as in `country`, e.g. \"DK\"",
        -    "type": "string"
        -  },
        -  "iban": {
        -    "description": "As in `iban`, e.g. \"DK5000400440116243\"",
        -    "type": "string"
        -  },
        -  "query": {
        -    "description": "Name, LEI or registration number, as in `query`, e.g. \"24256790\"",
        -    "type": "string"
        -  },
        -  "vatNumber": {
        -    "description": "As in `vatNumber`, e.g. \"DK24256790\"",
        -    "type": "string"
        -  }
        -}
      • removedInput schema / properties / companies / items / required
        Removed value: -[
        -  "query"
        -]
      • removedInput schema / properties / companies / items / type
        Removed value: -"object"
  3. 1 tool update
    • Changedcounterparty_check2 fields changed
      • addedInput schema / properties / companies
        Added value: +{
        +  "description": "Check a list of companies in one run instead of `query`: up to 10 objects with the fields above",
        +  "items": {
        +    "properties": {
        +      "country": {
        +        "description": "ISO 3166 alpha-2 code, as in `country`, e.g. \"DK\"",
        +        "type": "string"
        +      },
        +      "iban": {
        +        "description": "As in `iban`, e.g. \"DK5000400440116243\"",
        +        "type": "string"
        +      },
        +      "query": {
        +        "description": "Name, LEI or registration number, as in `query`, e.g. \"24256790\"",
        +        "type": "string"
        +      },
        +      "vatNumber": {
        +        "description": "As in `vatNumber`, e.g. \"DK24256790\"",
        +        "type": "string"
        +      }
        +    },
        +    "required": [
        +      "query"
        +    ],
        +    "type": "object"
        +  },
        +  "maxItems": 10,
        +  "type": "array"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "query"
        -]New value: +[]
  4. 3 tool updates
    • First observedcounterparty_check
    • First observedplan_official_records_query
    • First observedsanctions_screening

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.