Web3 Research MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchD | – |
| create-research-planD | – |
| research-with-keywordsD | – |
| update-statusD | – |
| fetch-contentD | – |
| search-sourceD | – |
| list-resourcesD | – |
| research-sourceD | – |
| research-tokenD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| token-research |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| research-status | |
| research-plan | |
| research-logs | |
| resources-list | |
| research-data |
TDQS
Scored across 9 tools
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.
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.
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.
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.