Skip to main content
Glama
traql MCP server

traql MCP server

Official

Related Servers

Alternatives to traql MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to assess the risk of crypto wallets, tokens, and smart contracts by providing read-only on-chain analysis, 0-100 risk scoring with explanations, fund tracing, and contract inspection before interaction.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to perform read-only on-chain risk screening, blacklist checks, and fund tracing across TRON and EVM chains, including rug-pull forensics and dirty-USDT detection. It also provides bilingual tool descriptions for Chinese-language agent ecosystems.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run pre-sign risk checks on transactions, approvals, EIP-712 signatures, token addresses, wallet approvals, sanctions screening, and prompt-injection texts, returning green/orange/red verdicts with machine-readable reason codes before signing.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Archived and no longer maintained. Tools and prices shown here are out of date. Use the maintained server: glama.ai/mcp/servers/OceanAlt666/oceanalt-aml-mcp (GitHub: OceanAlt666/oceanalt-aml-mcp).
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access real-time crypto risk intelligence with two tools: Flare for precursor detection and Core for overall risk environment assessment.
      4
      -

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target distinctly different entities: check_address evaluates a single address, while screen_transaction evaluates a transaction by scoring both sides. They are clearly separated by purpose and input requirements, with no overlapping functionality.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: check_address and screen_transaction. The verbs ('check' vs 'screen') are semantically appropriate and the noun targets (address, transaction) are clear, maintaining a uniform naming style.

    Tool Count4/5

    With only two tools, the server is compact but well-scoped for its narrow AML screening purpose. Each tool covers a fundamental operation (address check and transaction screening), so the count feels appropriate rather than insufficient, though it is below the typical 3-15 range.

    Completeness4/5

    The tool surface covers the primary use cases for AML risk assessment: pre-transaction screening and single-address checks. Minor gaps exist, such as lack of batch processing or historical investigation features, but these are not essential for the stated purpose and do not create dead ends in common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues