Everclear MCP Server
Related Servers
Alternatives to Everclear MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.43541 npm10MIT
- FlicenseNot gradedqualityDmaintenanceConnects Claude with Piriod.com API to manage invoicing and payments, enabling listing/creating invoices, searching customers, and viewing payments through natural language.-
- FlicenseAqualityDmaintenanceGives Claude access to Alchemy blockchain APIs by loading all API specs at startup and providing two tools: search and execute. Enables querying NFTs, token balances, transactions, and more via natural language.2-

Base MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceProvides onchain tools for Claude AI to interact with the Base blockchain and Coinbase API, enabling wallet management, fund transfers, and smart contract deployment.110 npm350MIT- AlicenseBqualityDmaintenanceEnables Claude to interact with Ethereum nodes, allowing users to check ENS token balances, view smart contract code, and decode transactions through natural language.51MIT
- AlicenseNot gradedqualityFmaintenanceProvides Claude with access to blockchain data and market prices via the OKX API, enabling operations like retrieving asset prices, transaction history, and executing swaps.3MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct resources and actions (intents vs invoices vs details vs quotes vs metrics vs conversions). The one real overlap is get_invoices and get_invoices_formatted, which return the same underlying invoice data with different formatting, so an agent could reasonably pick the wrong one. This is a minor boundary issue rather than widespread duplication.
Names follow a consistent snake_case get_/convert_ verb_noun pattern (get_intent_details, get_invoice_details, convert_chain_id_to_name). The only slight deviation is get_invoices_formatted using an adjective modifier rather than a plain noun, but the convention is still readable and predictable.
Eleven tools is well within the ideal 3-15 range and each maps to a distinct read/analytics or helper operation. The surface feels scoped to the Everclear domain without obvious filler.
The server covers the read/analytics lifecycle well: intents, invoices, invoice details, minimum amounts, route quotes, and liquidity/clearing metrics, plus conversion helpers. There are no write operations (submit intent, settle invoice), but as a monitoring/query surface the coverage is solid with only minor gaps.