cryptoapis-address-latest
OfficialRelated Servers
Alternatives to cryptoapis-address-latest
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying blockchains across EVM, Solana, Bitcoin/UTXO, and Cosmos through a unified interface, with tools for resolving addresses, checking balances, fetching transactions and blocks, reading contracts, decoding calldata, and building unsigned transfers.11 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying on-chain data (balances, transactions, token transfers, blocks) across 20+ EVM chains through natural language.61 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only cross-chain snapshot reports for 1–5 public EVM addresses on Ethereum, Base, Arbitrum One, and Polygon, including block numbers, EIP-7702 delegation indicators, contract-code sizes, fingerprints, and explorer links. It also supports obtaining live payment quotes in native USDC on Base and submitting a paid report request after user payment and signature, without moving funds or accessing private keys.MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying blockchain wallet token balances, net worth, token holders, and decoded transaction history across EVM chains via the Moralis Web3 Data API.145 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables blockchain forensics across multiple chains (Base, Ethereum, Arbitrum, Optimism, Polygon) with tools to trace transactions, cluster addresses, detect anomalies, and identify mixer usage.MIT
- FlicenseNot gradedqualityDmaintenanceProvides tools for querying onchain data across 12+ blockchain networks, including token balances, transaction analysis, and smart contract security auditing. It enables users to interact with multiple EVM-compatible chains and perform deep contract evaluations through natural language interfaces.1-
TDQS
Scored across 6 tools
Each tool is scoped to a distinct blockchain family (EVM, UTXO, Solana, XRP, Kaspa) plus a documentation tool, so the top-level boundaries are clear. The only mild ambiguity is that get-balance/list-transactions appear as sub-actions in five tools, so the agent must know which family a chain belongs to (e.g. tron living under the EVM tool is non-obvious).
Five tools follow a clean, predictable <chain>_address_latest pattern, making the family scope immediately readable. system_info is the single deviation, but it is a clearly different kind of tool so the break is understandable.
Six tools is well-scoped for an address-data API, with each chain family bundling its own actions rather than exploding into dozens of per-action tools. No tool feels redundant or filler.
Core address workflows are covered: balance, transactions, token transfers, nonce/sequence, and unconfirmed mempool transactions. Minor gaps exist — no UTXO/unspent-output listing, no token holdings for Solana/XRP chains beyond list-tokens, and Kaspa supports only balance plus transactions.