Which integrations are available for this server?

Enables the retrieval of cryptocurrency token data and market information from CoinMarketCap as part of a comprehensive research workflow for generating detailed reports.

How do I use Web3 Research MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Web3 Research MCP generate a detailed research report for Solana (SOL)" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Web3 Research MCP

by HaskellFan

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Web3 Research MCP

Deep Research for crypto - free & fully local 🧠

🚀 Preview

Preview Preview2

Related MCP server: Web3 Research MCP

🧠 Features

Comprehensive Research: Gather detailed information about any cryptocurrency token
Multi-Source Analysis: Research across multiple sources including CoinGecko, CoinMarketCap, DeFiLlama, and more
Structured Reporting: Generate detailed reports covering technical fundamentals, market data, social sentiment, and more
Resource Management: Automatically stores search results and content for reference
Status Tracking: Track research progress through different stages and sections

📋 Requirements

Node.js (v16 or higher)

🔧 Installation & Setup

Installing via Smithery

To install web3-research-mcp for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install web3-research-mcp --client claude

🔌 Using with Claude Desktop

Edit your Claude Desktop config file

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Add this to your Claude Desktop configuration file:

{
  "mcpServers": {
    "web3-research-mcp": {
      "command": "npx",
      "args": ["-y", "web3-research-mcp@latest"]
    }
  }
}

Then restart Claude Desktop

🔌 Using with Cursor

Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server Paste this into your Cursor ~/.cursor/mcp.json file. See Cursor MCP docs for more info.

{
  "mcpServers": {
    "web3-research-mcp": {
      "command": "npx",
      "args": ["-y", "web3-research-mcp@latest"]
    }
  }
}

Then restart Cursor

🛠️ Tools

create-research-plan

Creates a structured research plan for a token.

Parameters:

tokenName: Full name of the token
tokenTicker: Ticker symbol of the token

search

Performs a web search and returns the results.

Parameters:

query: Search query
searchType: Type of search (web, news, images, videos)

research-with-keywords

Searches for a token with specific keywords and saves the results.

Parameters:

tokenName: Name of the token
tokenTicker: Ticker symbol
keywords: Array of keywords to search for

update-status

Updates the status of a research section.

Parameters:

section: Section name to update (e.g., 'projectInfo', 'technicalFundamentals')
status: New status for the section (planned, in_progress, completed)

fetch-content

Fetches content from a URL and saves it as a resource.

Parameters:

url: URL to fetch content from
format: Output format (text, html, markdown, json)

list-resources

Lists all available resources that have been saved.

search-source

Searches for information about a token from a specific source.

Parameters:

tokenName: Name of the token
tokenTicker: Ticker symbol
source: Source to search (e.g., 'CoinGecko', 'DeFiLlama', 'News')

📝 Prompts

token-research

Initiates comprehensive research on a cryptocurrency token.

Parameters:

tokenName: Full name of the cryptocurrency token
tokenTicker: Ticker symbol of the token (e.g., BTC, ETH)

🧠 How It Works

When research begins, a structured plan is created covering all aspects of the token
The server performs searches across multiple sources for information
Search results are stored as resources that can be referenced
The research progresses through different sections, with status tracking
A comprehensive report is generated covering all aspects of the token

⚠️ Limitations

Some websites block web scraping, so direct content fetching may fail with 403 errors
Relies on search results which may not always be comprehensive
Rate limits may apply to search operations

📄 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Available Tools

9 tools

create-research-planD

ParametersJSON Schema

Name	Required	Description	Default
`tokenName`	Yes	Token name
`tokenTicker`	Yes	Token ticker symbol

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fetch-contentD

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes	URL to fetch content from (can be a resource:// URL)
`format`	No	Output format	markdown

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list-resourcesD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research-sourceD

ParametersJSON Schema

Name	Required	Description
`tokenName`	Yes	Name of the token
`tokenTicker`	Yes	Ticker symbol of the token
`source`	Yes	Single source to research

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research-tokenD

ParametersJSON Schema

Name	Required	Description
`tokenName`	Yes	Name of the token
`tokenTicker`	Yes	Ticker symbol of the token
`source`	Yes	Source to research (e.g., 'IQ Wiki', 'CoinMarketCap')

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research-with-keywordsD

ParametersJSON Schema

Name	Required	Description
`tokenName`	Yes	Name of the token
`tokenTicker`	Yes	Ticker symbol of the token
`keywords`	Yes	Keywords to search for

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchD

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Search query
`searchType`	No	Type of search	web

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search-sourceD

ParametersJSON Schema

Name	Required	Description
`tokenName`	Yes	Name of the token
`tokenTicker`	Yes	Ticker symbol of the token
`source`	Yes	Source to search (e.g., 'Dune', 'IQ Wiki', 'News')

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update-statusD

ParametersJSON Schema

Name	Required	Description	Default
`section`	Yes	Section name to update (e.g., 'projectInfo', 'technicalFundamentals')
`status`	Yes	New status for the section

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

9 tool updatesv1.0.1Feb 7, 2026
- First observedcreate-research-plan
- First observedfetch-content
- First observedlist-resources
- First observedresearch-source
- First observedresearch-token
- First observedresearch-with-keywords
- First observedsearch
- First observedsearch-source
- First observedupdate-status

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.6/5.0

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

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Hive Intelligence MCP A
xyz.hiveintelligence
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
Blockchain Cryptocurrency Web3 & Decentralized Tech
8218
TSUNG AI Research & Analysis B
io.github.a0985344368-glitch
Multi-LLM AI Research & Analysis — smart routing, consensus analysis, due diligence reports
Research & Data Autonomous Agents RAG Systems
2
Sofya A
co.sofya
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Search Browser Automation Web Scraping
42
mcp-crypto-toolkit A
io.github.nad33mahm3d
Live crypto prices, conversion, gas tracker, portfolio tools, and calculators for AI agents.
101

Related MCP Servers

Deep Research MCP Server
RAG Systems Web Scraping Search
teelaitila
A
license
Not graded
quality
C
maintenance
Enables iterative deep research by integrating AI agents with search engines, web scraping, and large language models for efficient data gathering and comprehensive reporting.
Updated 7 months ago (2026-01-28 10:48 UTC)
8
323
MIT
Web3 Research MCP
Web3 & Decentralized Tech Cryptocurrency Research & Data
aaronjmars
A
license
D
quality
A
maintenance
Deep Research for crypto - free & fully local 🧠
Updated 3 days ago (2026-09-03 14:17 UTC)
14
218
161
MIT
Netmind Web3 MCP Server
Web3 & Decentralized Tech Blockchain Cryptocurrency
protagolabs
F
license
Not graded
quality
C
maintenance
Provides 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.
Updated 2 months ago (2026-07-02 06:52 UTC)
-
market-data-mcp
Cryptocurrency Finance Search
aviman1109
A
license
Not graded
quality
D
maintenance
Integrates cryptocurrency market data from CoinGecko, the Fear & Greed Index, and CryptoPanic news into a single toolset for AI agents. It enables users to retrieve global market statistics, trending assets, coin-specific details, and real-time news feeds.
Updated 5 months ago (2026-03-26 02:38 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HaskellFan/web3-research-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server