Web3 Research MCP
Local, keyless MCP for structured crypto token research: web/news/image/video search plus CoinGecko and DeFiLlama data.
- Sato Score77
Web3 Research MCP is an open-source MCP server by aaronjmars, with last code activity on 2026-10-08 (Active). Latest release on 2026-07-30. Sato Score 77/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Web3 Research MCP →Last commit Oct 8, 2026 · Last release Jul 30, 2026 (v1.0.5) · ★ 168
Listed from github.com/aaronjmars/web3-research-mcp on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch Web3 Research MCP
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on aaronjmars/web3-research-mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
web3-research-mcp is a Model Context Protocol server that runs fully locally over stdio (via npx, no database or hosted service) to give an AI client a deep-research toolset for crypto: DuckDuckGo-based web/news/image/video search with page-content fetching, plus direct CoinGecko and DeFiLlama API tools, with results stored as referenceable MCP resources and a token-research prompt. Built and maintained by independent developer aaronjmars; no API keys are required.
Sato Score
77/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 19/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 13/15
- Independent verification
- 2/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.0.5 · as of 2026-09-26- Does it take your key?
- No key read found
- Does your key leave?
- Not observed
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from github.com/aaronjmars/web3-research-mcp on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | not stated | self-reported | github.com/aaronjmars/web3-research-mcp | as of 2026-10-15 |
| Verification status | Unverified — not independently reviewed | self-reported | github.com/aaronjmars/web3-research-mcp | as of 2026-10-15 |
| Recent activity | last release 2026-07-30 · last commit 2026-10-08 | observed | github.com/aaronjmars/web3-research-mcp | 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/aaronjmars/web3-research-mcp | 2026-07-21 |
| Website answers | answered (HTTP 200) | observed | github.com/aaronjmars/web3-research-mcp | 2026-10-15 |
| Daily check record | 89 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-26 |
| Key leaves the machine | not observed during install and start-uplater or triggered code paths are not covered | observed | satohub.ai | 2026-09-26 |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-26 |
| Deploys as | Local (stdio)confidence 0.60 | self-reported | github.com/aaronjmars/web3-research-mcp | as of 2026-07-14 |
| Works with | Claude Desktop, Cursor, Smithery, CoinGecko, CoinMarketCap, DeFiLlamaconfidence 0.85 | self-reported | github.com/aaronjmars/web3-research-mcp | as of 2026-10-03 |
| X account | https://x.com/aaronjmarsconfidence 0.80 | self-reported | github.com/aaronjmars/web3-research-mcp | as of 2026-10-03 |
| Sato Score | 77/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Jul 21, 2026
Runtime: node
npx -y web3-research-mcp@latest npx -y web3-research-mcp@latest
claude mcp add satohub-web3-research-mcp -- npx -y web3-research-mcp@latest
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 90
- Failed
- 1
- Their error
- 0
- Unattributed
- 1
State changed on 2026-09-21 (responding → unreachable from our probe), 2026-09-22 (unreachable from our probe → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Unknown
- Agent types
- MCP Server, Data Provider
- Open source
- Yes
- Deploys as
- Local (stdio)
- Works with
- Claude Desktop, Cursor, Smithery, CoinGecko, CoinMarketCap, DeFiLlama
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Web3 Research MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools
Recent Activity
All news →Releases and posts from Web3 Research MCP, pulled from its GitHub and X.
Listing History
Recorded changes to Web3 Research MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 3, 2026Auto-enriched: supported integrations, x url
- Jul 30, 2026New release published
- Jul 21, 2026Verified: deploy spec
- Jul 20, 2026Sato Score tier: Medium → HighScore 63 → 71.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: deployment options
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Web3 Research MCP
- Is Web3 Research MCP open source?
- Yes. Web3 Research MCP is open source under the MIT license; the repository is https://github.com/aaronjmars/web3-research-mcp. Checked as of 2026-10-15.
- Which chains does Web3 Research MCP support?
- Sato Hub has no confirmed chain list for Web3 Research MCP as of 2026-10-15; treat chain support as unknown.
- Is Web3 Research MCP still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-08 (last commit 2026-10-08, last release 2026-07-30), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Web3 Research MCP?
- node. Install: npx -y web3-research-mcp@latest. Entry: npx -y web3-research-mcp@latest. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y web3-research-mcp@latest).
- Is Web3 Research MCP verified on Sato Hub?
- Sato Hub holds one earned check for Web3 Research MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 77 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Web3 Research MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/web3-research-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.