traql
NPM · @TRAQL/MCP · SCANNED SEP 20
AML risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, Bitcoin
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to traql/mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · @traql/mcp
claude mcp add io-traql-mcp-server -- npx -y @traql/mcp
{
"mcpServers": {
"io-traql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@traql/mcp"
]
}
}
} {
"servers": {
"io-traql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@traql/mcp"
]
}
}
} codex mcp add io-traql-mcp-server -- npx -y @traql/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-traql-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@traql/mcp"
],
"enabled": true
}
}
} openclaw mcp add io-traql-mcp-server --command npx --arg -y --arg @traql/mcp
mcp_servers:
io-traql-mcp-server:
command: "npx"
args: ["-y", "@traql/mcp"] {
"McpServers": {
"io-traql-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@traql/mcp"
]
}
}
} assistant mcp add io-traql-mcp-server -t stdio -c npx -a -y @traql/mcp
{
"mcpServers": {
"io-traql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@traql/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 8 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.1 → 0.1.2 functional
- 7 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@traql/mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | traql/mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/traql/mcp-server/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 2758503294 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cecb6e85ddf134864f23b055ffeb50affcad7410746175a2fbd9e4a493fdd97d8ef3f5bc5249f70ea505955b6403b1931ec0d22cc714d6cdaace39ceb |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_address Check address risk ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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 | yes | Blockchain network the subject belongs to. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| subject | object | yes | Echo of the canonical subject that was scored. |
No examples provided.
screen_transaction Screen transaction risk ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| subject | object | yes | Echo of the canonical subject that was scored. |
No examples provided.
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.