@cryptoapis-io/mcp-aml
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRYPTOAPIS_API_KEY | No | Your Crypto APIs API key. Required if not provided via --api-key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| amlA | AML (Anti-Money Laundering) risk checks for addresses and transactions. Actions: • verify-address: Check if a blockchain address is flagged or associated with fraud, sanctions, ransomware, exploits, darknet markets, or other AML risk categories. Returns risk score, risk band, and the flagging sources. • screen-transaction: Screen a transaction against AML data. Returns whether the transaction is flagged, its risk score/band, and the flagged participant addresses with their roles, scores, severities and categories. • get-address-exposure: Get an address's exposure to risky entities/categories across the AML exposure graph. Params: blockchain, address. Costs 200,000 credits per request. • list-address-exposure-paths: List the paths connecting an address to risky entities in the AML exposure graph. Params: blockchain, address; optional rootAddress (only return routes originating from this flagged root address), limit (1-50, defaults to 10), startingAfter (pagination cursor). Costs 100,000 credits per page - pass the response's next cursor back as startingAfter to fetch subsequent pages. get-address-exposure and list-address-exposure-paths only support a subset of chains - see the blockchain parameter description. Note: the credit cost of these endpoints is significant — see credits below. Credits by action (source: OpenAPI): • get-address-exposure: 200000 • list-address-exposure-paths: 100000 • screen-transaction: 500000 • verify-address: 200000 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| system_infoA | CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check-aml-risk | Check the AML risk of a blockchain address or transaction |
| check-address-exposure | Check a blockchain address's exposure to risky entities via the AML exposure graph (200,000 credits per request; 100,000 credits per page for paths) |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-capabilities | Available AML tools, actions, and the blockchains screen-transaction and the exposure actions support |
TDQS
Scored across 2 tools
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.
`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.
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.
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.