anchain-data-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANCHAIN_APIKEY | Yes | Your AnChain 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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screen_ip_addressA | Analyze IP geolocation data and sanctions status to support regional compliance checks. Args: ip_address: IP address to screen (IPv4 format, e.g. 1.2.3.4) Cost: 5 credits |
| get_address_labelB | Retrieve the category label for a blockchain address, including the associated entity when available. Args: proto: Blockchain protocol (btc, eth, xlm, xmr, bnb, matic, avax, sol, trx, ada, dot, ltc, bch, algo, xrp) address: Blockchain address to query (e.g. 0x2f389ce8bd8ff92de3402ffce4691d17fc4f6535) Cost: 5 credits |
| get_address_risk_scoreA | Retrieve an address risk score (0-100), risk level (1-4), category, and associated entity. Args: proto: Blockchain protocol (btc, eth, xlm, xmr, bnb, matic, avax, sol, trx, ada, dot, ltc, bch, algo, xrp) address: Blockchain address to query (e.g. 1ECeZBxCVJ8Wm2JSN3Cyc6rge2gnvD3W5K) Cost: 10 credits |
| bulk_address_labelA | Retrieve address category labels and related entity information for multiple blockchain addresses (up to 10) in a single request. Args: proto: Blockchain protocol (btc, eth, xlm, xmr, bnb, matic, avax, sol, trx, ada, dot, ltc, bch, algo, xrp) addresses: List of blockchain addresses to query (1-10 addresses) Cost: 50 credits |
| bulk_address_risk_scoreA | Retrieve address risk scores, risk levels, and categories for multiple blockchain addresses (up to 10) in one request. Args: proto: Blockchain protocol (btc, eth, xlm, xmr, bnb, matic, avax, sol, trx, ada, dot, ltc, bch, algo, xrp) addresses: List of blockchain addresses to query (1-10 addresses) Cost: 100 credits |
| get_address_suspicious_activitiesA | Retrieve suspicious activity associated with a blockchain address, along with related risk scores, levels, and categories. Args: proto: Blockchain protocol (btc, eth, xlm, xmr, bnb, matic, avax, sol, trx, ada, dot, ltc, bch, algo, xrp) address: Blockchain address to query (e.g. 1ECeZBxCVJ8Wm2JSN3Cyc6rge2gnvD3W5K) Cost: 50 credits |
| get_transaction_detailB | Retrieve detailed on-chain information for a specific blockchain transaction. Args: proto: Blockchain protocol (btc, eth, xrp, hash) hash: Transaction hash (e.g. 0xfd04466bb91ec4270172acffe187eea57145a906de9b488a0f410ade1569760e) Cost: 50 credits |
| get_address_statsA | Retrieve statistical insights for a blockchain address, including transaction volume, frequency, and behavioral patterns. Args: proto: Blockchain protocol (btc, eth, xlm) address: Blockchain address to analyze (e.g. bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h) Cost: 100 credits |
| get_address_attributionA | Analyze inflow and outflow activity of blockchain wallet addresses with entity-based attribution and percentage breakdowns. Args: proto: Blockchain protocol (btc, eth, xlm) address: Blockchain address to query (e.g. bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h) Cost: 200 credits |
| auto_trace_addressA | Automatically trace the flow of transactions from a wallet address across multiple hops. May take up to 5 minutes. Args: proto: Blockchain protocol (btc, eth, trx, xrp) address: Blockchain address to trace (e.g. 1ECeZBxCVJ8Wm2JSN3Cyc6rge2gnvD3W5K) direct: Transaction direction filter (in, out) time_from: Start timestamp for analysis (Unix timestamp, e.g. 1577836800) time_to: End timestamp for analysis (Unix timestamp, e.g. 1609459200) Cost: 200 credits |
| get_transaction_graphA | Retrieve detailed transaction data with graph structures suitable for visualization and relationship analysis. Args: proto: Blockchain protocol (currently only eth supported) hash: Transaction hash (e.g. 0xfd04466bb91ec4270172acffe187eea57145a906de9b488a0f410ade1569760e) Cost: 100 credits |
| get_smart_contract_codeA | Analyze smart contract source code and related execution behavior to understand contract logic and activity. Args: proto: Blockchain protocol (eth, bnb) contract_address: Smart contract address to analyze (e.g. 0xe924a9989d5bf8e8dea744deb390e6f4015b470c) Cost: 300 credits |
| get_contract_transactionA | Retrieve detailed information for smart contract transactions, including input data, state changes, and execution results. Args: proto: Blockchain protocol (eth, bnb) transaction_hash: Transaction hash to analyze (e.g. 0xfd04466bb91ec4270172acffe187eea57145a906de9b488a0f410ade1569760e) Cost: 300 credits |
| screen_ofac_addressA | Check whether a blockchain address is associated with entities listed on the OFAC sanctions list. Args: address: Blockchain address to screen (e.g. 1ECeZBxCVJ8Wm2JSN3Cyc6rge2gnvD3W5K) Cost: 5 credits |
| search_ofacA | Search the OFAC sanctions database using exact field matching across names, identifiers, and related attributes. Args: type: Entity type (individual, entity, vessel, aircraft) name: Full name first_name: First name (for individuals) last_name: Last name (for individuals) id: Crypto wallet addresses or identification numbers address: Street address city: City name state: State or province country: Country or nationality Cost: 10 credits |
| fuzzy_search_ofacA | Perform fuzzy text matching across the OFAC sanctions database for names, addresses, and related fields. Args: q: Fuzzy search query for broad text matching (e.g. bank corporation) Cost: 100 credits |
| screen_global_sanctions_addressA | Check whether a blockchain address appears on international sanctions lists from multiple countries and organizations. Args: address: Blockchain address to screen (e.g. 0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9) dataset: Global sanctions dataset to search in (global, au, ca, ch, eu, gb, il, jp, un, za, zm). Default: global Cost: 10 credits |
| search_global_sanctionsA | Search international sanctions databases using exact field matching across multiple jurisdictions. Args: dataset: Global sanctions dataset to search in (global, au, ca, ch, eu, gb, il, jp, un, za, zm). Default: global type: Entity type (individual, entity, vessel, aircraft) name: Entity name address: Physical address country: Country or nationality birth_date: Date of birth legal_form: Legal entity type registration_number: Registration number incorporation_date: Incorporation date jurisdiction: Incorporation jurisdiction wallet: Cryptocurrency wallet addresses Cost: 20 credits |
| fuzzy_search_global_sanctionsA | Perform fuzzy text matching across international sanctions databases for broader and more comprehensive coverage. Args: q: Fuzzy search query (e.g. Kesklinna) dataset: Global sanctions dataset to search in (global, au, ca, ch, eu, gb, il, jp, un, za, zm). Default: global Cost: 200 credits |
| get_crypto_newsA | Retrieve cryptocurrency and blockchain-related news and market information from multiple sources. Args: query: Search query for cryptocurrency news (e.g. bitcoin price) category: News category filter (general, bitcoin, ethereum, defi, nft, regulation, exchange, mining) Cost: 20 credits |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools target distinct resources or actions, such as address labeling, risk scoring, transaction details, and sanctions database searches. However, certain tools like get_transaction_detail and get_contract_transaction may be confused, though descriptions provide some clarity.
Naming patterns are mixed: most tools use get_ or search_ prefixes, but there are deviations like bulk_address_label, auto_trace_address, and fuzzy_search_ofac. The lack of a uniform verb_noun structure makes the set slightly inconsistent.
With 20 tools, the server is somewhat heavy but not excessive for its dual focus on blockchain analytics and sanctions screening. Several tools are near-duplicates (exact vs. fuzzy search, bulk vs. single address), which could be consolidated.
The tool surface covers core workflows, including address analytics, risk scoring, transaction tracing, and sanctions screening. Gaps include batch sanctions screening and comprehensive address transaction history, but these are not critical for the server's apparent purpose.