A
licenseB
qualityD
maintenanceProvides AI agents with research tools for AI agent ecosystem analysis, DeFi protocol analysis, and general market research.
3
29 npm
MIT
Web3 Research MCP
by HaskellFan
Related Servers
Alternatives to Web3 Research MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides a comprehensive suite of Web3 tools for querying token addresses, news summaries, and real-time market data via CoinGecko. It also facilitates DeFi operations including token price tracking, pool information, and swap quotes through Sugar DeFi integration.-
- AlicenseBqualityBmaintenanceEnables AI tools to access local crypto market data, run analyses, perform 66-item deep research, search RAG context, and retrieve generated reports and prompts via MCP.10MIT
- AlicenseDqualityAmaintenanceDeep Research for crypto - free & fully local ðŸ§1468 npm162MIT
- AlicenseNot gradedqualityDmaintenanceEnables iterative deep research by integrating AI agents with search engines, web scraping, and large language models for efficient data gathering and comprehensive reporting.11 npm322MIT
- FlicenseAqualityCmaintenanceEnables AI assistants to perform institutional research and due diligence by retrieving, extracting, validating, and citing data from public sources, then generating reports in markdown, HTML, or PDF.23-
TDQS
D1.6/5.0
Scored across 9 tools
Disambiguation2/5
Multiple tools have unclear boundaries and overlapping purposes. 'search', 'search-source', 'research-with-keywords', and 'fetch-content' all appear to involve finding information, while 'research-source' and 'research-token' seem similar in focus. Without descriptions, it's difficult to distinguish their specific use cases, leading to potential misselection.
Naming Consistency3/5
The naming conventions are mixed but still readable. Most tools use kebab-case (e.g., 'create-research-plan'), but there are inconsistencies like 'fetch-content' vs. 'list-resources' (different verb styles). While not chaotic, the lack of a uniform pattern reduces predictability across the tool set.
Tool Count4/5
With 9 tools, the count is reasonable for a research-focused server. It's slightly on the higher side but still manageable, suggesting a well-scoped set that covers various aspects of web3 research without being overwhelming. The number aligns with typical server scopes of 3-15 tools.
Completeness3/5
Inferring from tool names, the domain appears to be web3 research operations. There are notable gaps in coverage: tools like 'create-research-plan' and 'update-status' suggest lifecycle management, but missing operations like delete or modify research plans indicate incomplete CRUD coverage. The set supports core workflows but has dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues