# traql (npm · @traql/mcp)

AML risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, Bitcoin

- Trust score: 92/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@traql/mcp`: 92/100 (this document), [markdown](https://verifymcp.io/servers/io-traql-mcp-server/traql-mcp.md), [page](https://verifymcp.io/servers/io-traql-mcp-server/traql-mcp)

## Channel facts

- Registry: `npm`
- Package: `@traql/mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to traql/mcp-server).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 609 tokens (~304/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the traql MCP server?

traql runs locally as an npm package, launched with npx -y @traql/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add io-traql-mcp-server -- npx -y @traql/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-traql-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@traql/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-traql-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@traql/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-traql-mcp-server -- npx -y @traql/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-traql-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@traql/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-traql-mcp-server --command npx --arg -y --arg @traql/mcp
```

### Hermes

```yaml
mcp_servers:
  io-traql-mcp-server:
    command: "npx"
    args: ["-y", "@traql/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-traql-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@traql/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-traql-mcp-server -t stdio -c npx -a -y @traql/mcp
```

### Other

```json
{
  "mcpServers": {
    "io-traql-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@traql/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 87, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-08 (score 71, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-09-07 (score 86, +1)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (2)

### `check_address` (~225 tokens)

Check address risk

Score a single crypto address for AML and compliance risk.

Returns a risk score from 0 (clean) to 100 (critical), the band it falls into, and the risk categories that drove it — sanctions, mixer, scam, darknet, stolen_funds, ransomware, high_risk_exchange and others. With an API key configured, the response also itemizes every contributing signal with its data source, severity and confidence, so the verdict can be explained rather than just asserted.

Use it before sending funds to an unfamiliar address, to triage an address a user pasted, to check a counterparty in an investigation, or to vet a deposit address. Covers Ethereum, BSC, TRON, TON and Bitcoin. Each call consumes one check from the configured traql account.

Input parameters:

- `address` (string, required): Address in the chain's native format: 0x-hex for ethereum and bsc, base58 starting with T for tron, EQ/UQ for ton, and legacy or bech32 for bitcoin.
- `chain` (string, required): Blockchain network the subject belongs to.

Output parameters:

- `result` (object)
- `subject` (object): Echo of the canonical subject that was scored.

### `screen_transaction` (~317 tokens)

Screen transaction risk

Screen a transaction for AML and compliance risk by scoring both sides of the transfer.

Two modes, chosen by which arguments are given:
\- Pre-flight — pass `from` and `to` (optionally `amount` and `asset`) to screen a transfer before it is broadcast. Works on every supported chain.
\- By hash — pass only `tx_hash` to look up a transaction that is already on-chain. Supported on ethereum, bsc, tron and ton.

Returns the same score, band, flags and itemized signals as an address check, with each signal marked as applying to the sending or receiving side. Use it as a pre-send safety gate, or to review a payment that already went out. Each call consumes one check from the configured traql account.

Input parameters:

- `amount` (string): Optional transfer amount as an integer string in the asset's base units (for example 1000000 for 1 USDT, which has 6 decimals). Never a decimal fraction.
- `asset` (string): Optional asset or token symbol being transferred, for example USDT.
- `chain` (string, required): Blockchain network the subject belongs to.
- `from` (string): Sender address, for screening a transfer that has not been broadcast yet.
- `to` (string): Recipient address, for screening a transfer that has not been broadcast yet.
- `tx_hash` (string): Hash of an already-broadcast transaction. Mutually exclusive with `from`/`to`. Supported on ethereum, bsc, tron and ton only.

Output parameters:

- `result` (object)
- `subject` (object): Echo of the canonical subject that was scored.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-traql-mcp-server/traql-mcp#diagnostics

## Score history

- 2026-09-20: 92
- 2026-09-19: 91
- 2026-09-18: 91
- 2026-09-17: 90
- 2026-09-16: 90
- 2026-09-15: 90
- 2026-09-14: 89
- 2026-09-13: 89
- 2026-09-12: 88
- 2026-09-11: 88
- 2026-09-10: 87
- 2026-09-09: 87
- 2026-09-08: 71
- 2026-09-07: 86
- 2026-09-06: 85
- 2026-09-05: 85
- 2026-09-04: 84
- 2026-09-03: 84
- 2026-09-02: 83
- 2026-09-01: 83
- 2026-08-31: 83
- 2026-08-30: 82
- 2026-08-29: 82
- 2026-08-28: 81
- 2026-08-27: 81
- 2026-08-26: 80
- 2026-08-25: 78
- 2026-08-24: 78
- 2026-08-23: 52

## Common questions

### What is the traql MCP server?

traql is an MCP server listed in the public MCP registry as io.traql/mcp-server. AML risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, Bitcoin. This page covers its npm package (@traql/mcp).

### Is the traql MCP server safe to use?

traql scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the traql MCP server expose?

traql exposes 2 tools: check_address, screen_transaction. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.

### Is the traql MCP server still maintained?

traql is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the traql MCP server under?

traql declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@traql/mcp
- Socket report: https://socket.dev/npm/package/@traql/mcp
- Repository: https://github.com/traql/mcp-server
- Website: https://traql.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-traql-mcp-server/traql-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-traql-mcp-server/traql-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-traql-mcp-server/traql-mcp