near-contract
Related Servers
Alternatives to near-contract
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop and MCP clients to interact with NEAR blockchain accounts for balance checks, account info, access keys, transaction status, and sending signed transactions.MIT
- FlicenseAqualityDmaintenanceEnables Claude to access real-time NEAR DeFi data for yield comparisons, staking analysis, swap routing, and lending rates, helping users make informed DeFi decisions.5-
- FlicenseAqualityDmaintenanceEnables AI assistants to deploy, initialize, and upgrade NEAR smart contracts with cost estimation and status checks.5-
- 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
- AlicenseBqualityDmaintenanceProvides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.43558 npm10MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to access, analyze, and visualize Solana blockchain data through natural language conversations.18-
TDQS
Scored across 5 tools
Tools are mostly distinct: metadata, state, view methods, interface explanation, and transaction decoding each target a different aspect. The slight overlap between get_contract_metadata and explain_contract_interface (both reveal methods) is mitigated by metadata being raw and explain being high-level.
All tool names follow a consistent verb_noun pattern in snake_case: get_contract_metadata, call_view_method, decode_transaction, get_contract_state, explain_contract_interface. No mixed conventions or ambiguous verbs.
Five tools is well-scoped for a contract inspection/analysis server. Each tool serves a clear purpose without redundancy, and the count is within the ideal range for a focused MCP server.
The tool surface covers the core needs for understanding NEAR contracts: metadata, raw state, view methods, interface explanation, and transaction decoding. A minor gap is the lack of a tool to simulate or estimate gas for view calls, but the current set is coherent and functional.