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.34 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying on-chain data (balances, transactions, token transfers, blocks) across 20+ EVM chains through natural language.150 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.259 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 gradedqualityCmaintenanceProvides 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 maps cleanly to a distinct blockchain family (EVM, UTXO, Solana, XRP, Kaspa) plus a reference tool, and the descriptions explicitly enumerate supported chains so overlaps are avoided. The only friction is that an agent must know which family a given chain belongs to before picking a tool (e.g. tron lives under the EVM tool), which is a mild mapping burden rather than true ambiguity.
Five tools follow an identical <family>_address_latest pattern, which is highly predictable and readable. system_info is the sole deviation, though it is a genuinely different kind of tool (static reference) so the break is defensible.
Six tools is well-scoped for an 'address latest data' server, with one tool per chain family plus a docs tool. Each tool earns its place, and consolidating the per-action operations (get-balance, list-transactions, etc.) into action parameters keeps the surface compact rather than exploding into dozens of near-duplicate tools.
Coverage is solid and reasonably symmetric: every family offers balance plus transaction listing, with family-specific extras (next-nonce, internal transactions, token transfers, unconfirmed txs, next-sequence). Gaps are minor — Kaspa is thin (balance + transactions only), there is no address validation/metadata tool, and webhook/callback management is described in system_info but has no corresponding tool.