Skip to main content
Glama
CryptoAPIs-io

@cryptoapis-io/mcp-aml

Official

Related Servers

Alternatives to @cryptoapis-io/mcp-aml

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      MCP server for AML/KYT crypto wallet screening, enabling AI clients to check wallet risk scores, source-of-funds tags, activity dates, and volume totals via Satoshkin backend.
      1
      38 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server for anti-money laundering (AML) compliance, including customer due diligence, transaction monitoring, and SAR filing, compliant with 6AMLD, UK MLR 2017, and FinCEN.
      4
      39 PyPI
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Crypto APIs Utils, enabling address validation, raw transaction decoding, and XRP X-Address encoding/decoding for UTXO, EVM, and XRP blockchains.
      5
      31 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Infinihash KYT providing real-time blockchain transaction monitoring, sanctions screening, and SAR generation. It enables MCP-compatible agents to screen wallets against OFAC SDN and generate compliance cases.
      10
      41 PyPI
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables blockchain AML screening of addresses in plain language inside any MCP client, covering sanctions and freeze checks, risk scoring, fund tracing, and counterparty classification across bitcoin, ethereum, bsc, and tron. Works without an account, with an optional API key that lifts rate limits and unlocks outgoing tracing.
      3
      24 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: `aml` performs blockchain AML risk checks and `system_info` returns reference documentation without API calls. An agent can easily choose between them. The multiple AML actions are bundled under one tool, but that is an intra-tool concern rather than tool-selection ambiguity.

    Naming Consistency3/5

    `system_info` uses a snake_case noun phrase while `aml` is a bare acronym, so the two names do not follow a single predictable pattern. Both remain readable and reasonably descriptive, but the convention is mixed.

    Tool Count3/5

    Two tools is on the thin side for the stated AML purpose, especially since one is purely reference documentation. The functional surface is effectively a single `aml` tool with four actions, making the overall offering borderline minimal rather than well-scoped.

    Completeness4/5

    The AML surface covers address verification, transaction screening, address exposure, and exposure-path discovery, which is solid coverage of the core AML workflow. Minor gaps exist, such as batch screening or broader entity lookup, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues