Skip to main content
Glama
aaronjmars

Web3 Research MCP

by aaronjmars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Web3 Research MCP

No user-submitted related servers found.

    Related Servers

    • Web3 Research MCP

      HaskellFan
      A
      license
      D
      quality
      D
      maintenance
      Enables deep research into cryptocurrency tokens by gathering data from multiple sources like CoinGecko and DeFiLlama to generate structured reports. It allows users to track research progress, fetch web content, and manage resources locally for comprehensive crypto analysis.
      9
      27 npm
      4
      Apache 2.0

    • deeplook

      OSOJDJD
      A
      license
      A
      quality
      C
      maintenance
      Researches any company in ~10 seconds using 10 data sources. Returns structured reports with bull/bear verdict for stocks, crypto, and private companies.
      2
      12
      AGPL 3.0

    • onvexia

      faraz152
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables crypto research and market intelligence through 66 read-only tools covering sentiment, whale tracking, on-chain flows, influencer accuracy, and screening across 2,300+ coins, allowing AI agents and traders to verify hype, accumulation, and momentum without an API key.
      MIT

    • crypto-deep-research

      alikula37
      A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.5/5.0

    Scored across 14 tools

    Disambiguation2/5

    Multiple tools appear to serve overlapping purposes: 'search', 'search-source', 'coingecko-search', and 'defillama-search' are hard to distinguish by name alone. Similarly, 'research-source', 'research-token', and 'research-with-keywords' blur together without descriptions to clarify their exact roles.

    Naming Consistency2/5

    Tool names mix kebab-case verbs like 'fetch-content' and 'create-research-plan' with noun-only names like 'coingecko-data' and 'defillama-search', plus a bare generic 'search'. There is no consistent verb_noun or domain-prefixed pattern across the set.

    Tool Count3/5

    Fourteen tools is within a reasonable range for a research-oriented server, but several names appear to cover nearly identical actions, making the set feel padded. The count itself is not extreme, but the apparent duplication reduces the sense that each tool earns its place.

    Completeness3/5

    The set covers a plausible web3 research workflow: planning, searching, fetching content, researching tokens/sources, status updates, and pulling market data. However, there are notable gaps in explicit output/result management and no clear end-to-end lifecycle, making completeness mediocre.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources