Adamik MCP Server
OfficialRelated Servers
Alternatives to Adamik MCP Server
No user-submitted related servers found.
Related Servers
AlicenseBqualityDmaintenanceEnables comprehensive interaction with the Zetrix blockchain including account operations, transactions, smart contracts, WebSocket real-time updates, and contract development tools through Claude Desktop.4491 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Stacks blockchain through Claude Desktop. Manage wallets, trade tokens on DEXs, stack STX for Bitcoin rewards, and track portfolio—all through natural conversation.30 npm6MIT
- AlicenseBqualityDmaintenanceProvides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.435110 npm10MIT
- FlicenseCqualityDmaintenanceEnables Claude Desktop to interact with the VeChain blockchain through natural language commands for token transfers, DEX trading, cross-chain bridges, NFT management, and VeBetter DAO operations.934-
- AlicenseNot gradedqualityDmaintenanceEnables users to interact with multiple blockchains including Solana, Ethereum, Cardano, THORChain, XRP Ledger, TON, and UTXO chains through simple RPC endpoints for balances, transactions, swaps, and network queries.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn MCP server that connects Claude for Desktop with blockchain functionality, allowing users to check balances and send tokens on EVM and Solana chains through natural language interactions.-
TDQS
Scored across 12 tools
Most tools have distinct purposes, but there is some overlap between getAccountHistory and getTransactionDetails, which could cause confusion about which to use for transaction-related queries. Additionally, getApiSpecification is a broad reference tool that might overlap in utility with other tools like listFeatures or encodeTransaction for schema details, though its comprehensive nature helps differentiate it.
All tool names follow a consistent verb_noun pattern (e.g., broadcastTransaction, deriveAddress, encodeTransaction), using camelCase uniformly throughout. This predictability makes it easy for agents to understand and navigate the tool set without confusion from mixed naming conventions.
With 12 tools, the count is well-suited for the server's purpose of blockchain operations, covering key actions like transaction handling, account management, and chain information. Each tool serves a specific function, and there is no bloat or missing critical tools, making the scope appropriate and manageable.
The tool set provides comprehensive coverage for blockchain interactions, including transaction encoding/broadcasting, account state/history retrieval, chain and token details, and API specifications. It supports all major transaction types and includes critical utilities like readMeFirst for guidance, leaving no obvious gaps for agents to perform typical blockchain operations.