F
licenseA
qualityD
maintenanceEnables Claude to interact with NEAR smart contracts: read state, call view methods, decode transactions, and explain contract interfaces.
5
-
NEAR Contract Deployer MCP Server
by jim-agent
Related Servers
Alternatives to NEAR Contract Deployer MCP Server
No user-submitted related servers found.
Related Servers
MIDL MCP Serverofficial
FlicenseAqualityDmaintenanceEnables AI assistants to interact with the MIDL blockchain, supporting smart contract deployment, balance queries, asset bridging, Bitcoin Rune management, and more through natural language.291-- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Solana blockchain, manage accounts and tokens, and develop and deploy smart contracts end-to-end.4-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to audit, migrate, scaffold, and manage TON smart contracts using the TON Dev Skills platform.10 npm1MIT
- AlicenseAqualityDmaintenanceEnables NEAR wallet operations including wallet creation, balance checking, and transaction signing for agent workflows.333 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to audit Solidity smart contracts for security vulnerabilities, fetch verified source code from block explorers, decode calldata, and estimate gas costs across major EVM networks.4MIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct phase in the contract lifecycle: deploy creates, initialize configures, upgrade replaces, status checks, and cost estimates. There is no overlap or ambiguity between them.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (deploy_contract, initialize_contract, upgrade_contract, get_deployment_status, estimate_deployment_cost). The pattern is uniform and predictable.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of managing NEAR contract deployments. Each tool is necessary and there is no redundancy or bloat.
Completeness5/5
The server covers the full deployment lifecycle: estimation, deployment, initialization, upgrading, and status checking. There are no obvious gaps for its stated purpose, as contract interaction beyond deployment is out of scope.
Maintenance
ActivityInactive
ResponsivenessNo issues