EdgeDepth Research

What EdgeDepth Research does

The EdgeDepth Research MCP server gives MCP clients access to EdgeDepth's recorded-market research system for Binance USDT-M crypto perpetuals. It is designed for studies that need an exact condition, a defined eligible population, forward outcomes, and an auditable result rather than a single illustrative chart or example.

The server can describe the available feature grammar and research universe, turn a natural-language request into a proposed query document, execute a research_query.v2 document, and continue paginated scans. It also supports event-focused analysis, including screenshot grounding, move investigation, point-in-time feature snapshots, base rates, commonality, cohort comparisons, and stratified outcomes.

How it works

EdgeDepth Research MCP server uses one tool core through hosted Streamable HTTP or local stdio. The hosted endpoint is https://mcp.edgedepth.com/mcp and uses browser authorization. Local execution runs the npm package with npx and an API key.

A typical workflow starts by checking the grammar or interpreting the research question. prepare_study can validate a structured scope, predicates, and outcome and return an unrun definition with an allowance estimate. interpret_prose produces a proposed query but does not execute it. After approval, run_scan executes the unchanged document. next_page uses the cursor returned by a previous scan; cursors should not be constructed manually.

Scan-family responses are projected by default to reduce client context usage. Options such as full_rows, full_outcomes, and full_counts recover additional detail where supported. Counts, denominators, exclusions, outcome coverage, and the reproducibility key remain part of the result contract.

Setup and configuration

For hosted use, add the MCP URL to a compatible client and complete the EdgeDepth browser authorization flow. Cursor uses an MCP entry with a url, while Codex uses an mcp_servers configuration and codex mcp login edgedepth.

For local stdio, install nothing permanently: run npx -y @edgedepth/research-mcp with EDGEDEPTH_API_KEY set to a key created on the EdgeDepth Developer page. Node.js 20 or newer is required. The research:read scope covers recorded-data tools; research:interpret is additionally needed for interpret_prose.

Tools and capabilities

• Inspect feature IDs, types, ranges, operators, windows, sequence rules, limits, and error codes with list_features.
• Check the research universe and coverage with list_instruments.
• Run scans, retrieve pages, and compare matched predicates with run_scan, next_page, and run_cohort.
• Analyze recorded events with ground_screenshots, investigate_move, and snapshot_at.
• Measure prevalence, intersections, stratified populations, and outcome-first patterns with base_rate, commonality, run_stratified, and outcome_first.
• Retrieve a published report using its eight-character canonical hash with get_report.

Limitations and notes

The EdgeDepth Research MCP server is research-only. Its tools do not trade, change alerts, or publish reports. Fresh scans, cohort calculations, and stratified computations may consume research allowance units, and the response identifies that side effect. prepare_study, interpret_prose, and screenshot grounding are described as free where applicable.

Outcome fields cannot be used as scan filters, which prevents lookahead selection in the supported workflow. Missing data is represented as absent rather than silently converted to zero. Page rows are examples; population counts and outcome denominators should be used for conclusions. The optional private Radar pilot can save account-owned hypotheses only with the separate research:hypotheses permission.