Skip to main content
Glama

Server Details

Checks names against OFAC, UK, EU, UN and more sanctions lists; returns scored possible matches.

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-06-18
URL
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a clearly distinct action and resource: account balance, stored record retrieval, source-list metadata, and name screening. There is no meaningful overlap that would cause an agent to select the wrong tool.

Naming Consistency5/5

All four tools use a consistent snake_case verb_noun pattern: get_balance, get_record, list_sources, and screen_names. The convention is predictable throughout.

Tool Count5/5

Four tools are well-scoped for a focused sanctions-screening API: one primary action, record lookup, source metadata, and balance/usage. Each tool has a clear reason to exist.

Completeness4/5

The core workflow is covered: list sources, screen names, retrieve a resulting record, and check credits. A minor gap is the lack of a way to list or search prior screening records without already knowing a record id.

Available Tools

4 tools
get_balanceGet Credit BalanceA
Read-onlyIdempotent
Inspect

Retrieve the credit balance for your API key and its latest credit movements. This tool is free to use.

Inputs: no named parameters. Returns: object

get_recordGet Screening RecordB
Read-onlyIdempotent
Inspect

Fetch a previously stored screening record by its record id. This tool is free to use.

Inputs: record_id (required). Returns: object

list_sourcesList Source ListsA
Read-onlyIdempotent
Inspect

The list_sources tool provides the 10 official sanctions lists and their data-as-of dates from the current daily snapshot. This tool is free to use and does not require an API key.

Inputs: no named parameters. Returns: object

screen_namesScreen NamesAInspect

Sanctions screening of 1 to 100 names against 10 official lists. The response includes a record id, the snapshot version, the data-as-of date for each source list, and the matching engine version. Each screened name costs one credit. Hits are candidates for human review and require further assessment.

Inputs: names (required), threshold, idempotency_key. Returns: object

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables screening names and batches against global sanctions, PEP, and watchlists for AML compliance, returning scored matches.
      270 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Screens names and companies against OFAC, EU, UK, and UN sanctions lists with fuzzy-match scores, supporting bulk lookups for AML/KYC checks. Data is sourced directly from official government lists and cached for fast repeat checks.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Screens person, company, vessel and aircraft names against the U.S. Treasury OFAC SDN sanctions list and explains every potential match: name-part scores, aliases, and date-of-birth or country conflicts. Runs locally with no API key; names never leave your machine.
      5
      1
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources