RootData MCP Server
Related Servers
Alternatives to RootData MCP Server
No user-submitted related servers found.
Related Servers
FlicenseAqualityBmaintenanceA server that exposes blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol, enabling AI agents and tools to access and analyze blockchain information contextually.1845-- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server utilizing Claude AI for generating intelligent queries and offering documentation assistance based on API documentation analysis.7 npm3MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to access Flow blockchain data and perform operations such as checking balances, resolving domains, executing scripts, and submitting transactions.1-
- FlicenseBqualityDmaintenanceA Model Context Protocol server providing access to WeWork project management data, enabling project search, task analysis, and statistics retrieval through Claude and other LLM clients.6-
- AlicenseBqualityFmaintenanceA Model Context Protocol server that connects Claude to Heurist Mesh APIs, providing access to various blockchain and web3 tools including cryptocurrency data, token security, Twitter intelligence, and web search capabilities.2067MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query blockchain chain data, including chain details, RPC endpoints, and chain relationships, through a Model Context Protocol server.5MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_organization retrieves VC details, get_project retrieves project details, and search performs keyword-based searches across multiple entity types. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific objectives.
All tool names follow a consistent verb_noun pattern: get_organization, get_project, and search. The naming is uniform, using snake_case throughout, with clear and predictable verbs that accurately describe each tool's action.
With only 3 tools, the server feels thin for a data-focused domain like VC and project details. While the tools cover basic retrieval and search, the scope suggests that additional operations (e.g., listing, filtering, or updating) might be expected, making the count borderline for comprehensive coverage.
The server provides read operations (get and search) but lacks create, update, or delete tools, which are typical for data management. This creates notable gaps in lifecycle coverage, as agents cannot modify or add data, limiting the server to query-only functionality.