Skip to main content
Glama
atomno-mcp

io.github.atomno-mcp/mcp-sanctions

by atomno-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.atomno-mcp/mcp-sanctions

No user-submitted related servers found.

    Related Servers

    • opensanctions-mcp

      scka-de
      A
      license
      A
      quality
      D
      maintenance
      MCP server for sanctions screening and PEP checks via OpenSanctions API. Search entities, match against 320+ sanctions lists, and run compound compliance investigations with AI agents.
      6
      39 npm
      MIT

    • Compliance & Sanções

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables due diligence and KYC by querying PEPs, national and international sanctions, debarment lists, arrest warrants, criminal records, leniency agreements, and forced labor registries via hosted, prepaid read-only MCP tools.
      MIT

    • mcp-sanctions-check

      HaveBlue997
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for OFAC SDN sanctions screening. Check names against US Treasury sanctions lists with automatic cache refresh. No API key needed for the check itself.
      MIT
    • mcp-dilisense by pipeworx-io

      mcp-dilisenseofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables sanctions, PEP, criminal, and adverse-media screening for individuals and entities, including broad watchlist checks across vessels and aircraft for AML/KYC compliance.
      380 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct by target: person, entity, INN, foreign-agent registry, and watchlist metadata. However, screen_person and screen_foreign_agent overlap for individuals, and screen_inn can cover both persons and entities when an INN is available.

    Naming Consistency5/5

    All tools use a consistent verb_noun snake_case pattern: screen_* for screening actions and list_watchlists for metadata. The naming is predictable and easy to navigate.

    Tool Count5/5

    Five tools is a well-scoped size for a sanctions screening server. Each tool addresses a common query path, and none feels redundant or unnecessary.

    Completeness4/5

    Core person, entity, and INN screening are covered, plus watchlist metadata. Minor gaps exist, such as batch screening, screening by passport/document, or OGRN-only lookup, but agents can usually work around them with the available tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources