In-depth architectural comparison of the Web3 Research MCP and EdgeDepth Research MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Web3 Research MCP
Finance & Fintech · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
EdgeDepth Research
Finance & Fintech · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Web3 Research MCP if you need specialized Finance & Fintech tools running via a local process. Choose EdgeDepth Research if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Web3 Research MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: COINGECKO_API_KEY.
Primary tools included: Multi-source crypto token data aggregation, Structured reporting of technical, market, and social info, Local operation with no external data transmission.
Web3 Research MCP is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, EdgeDepth Research belongs to Finance & Fintech using local stdio subprocess. Select Web3 Research MCP when you need capabilities focused on finance & fintech and EdgeDepth Research when you require tools for finance & fintech.
Returns the closed grammar registry: feature ids, types, ranges, operators, windows, sequence rules, limits, and error codes.
list_instruments
Returns the research universe and coverage. The default is a compact summary; use `symbols: [...]` for selected full records or `full: true` for the verbatim canonical universe.
interpret_prose
Turns prose into a proposed query document. It does not execute the query. Optional `time_zone` accepts an IANA time zone for calendar planning.
run_scan
Executes a `research_query.v2` document and returns canonical result bytes with counts, denominators, outcomes, the unconditional same-scope reference, and the reproducibility key.
next_page
Continues a prior scan with its opaque cursor. Never construct cursors manually.
snapshot_at
Reads registry feature values, window aggregates, and fired rules as of a recorded moment.
base_rate
Counts matches and eligible buckets for one clause over a window.
commonality
Finds the deterministic intersection across multiple moments with selection-bias caveats included.
get_report
Retrieves a published report by its 8-character canonical hash.
run_cohort
Compares what followed every match with what followed every other eligible predicate-false bucket.
run_stratified
Partitions one matched population at its existing anchors into split-true, split-false, and split-absent outcome summaries.