Introducing DEHY MCP — the data layer, native to Claude & CursorLearn more →

Developers

Build on the filing layer.

A versioned REST API and an MCP server over the same structured, scored record that powers the app. Your models, our data — grounded, never scraped.

DEHY MCP

The data layer, native to your agent.

Expose filings, holdings, conviction and fundamentals to Claude, Cursor and ChatGPT as tools — the model picks the tool, never writes SQL, and every answer is grounded.

$npx -y @dehy-mcp/server@latest
Crest — grounded answers from the live record

REST API

Every surface, one versioned endpoint away.

GET/api/v1/filings
Search and page every filing — by form, issuer, score, date.
GET/api/v1/conviction/{ticker}
The composite 0–100 conviction index for a name.
GET/api/v1/insiders/{cik}
Scored Form 4 activity for a reporter or issuer.
GET/api/v1/13f/{cik}
A filer’s holdings and quarter-over-quarter changes.
GET/api/v1/macro/positioning
Cross-asset CFTC positioning and central-bank stance.
Example
curl https://dehy.io/api/v1/conviction/NVDA \
  -H "Authorization: Bearer $DEHY_KEY"

{
  "ticker": "NVDA",
  "ici": 71,
  "label": "bullish",
  "insider": 18,
  "institutional": 22,
  "as_of": "2026-09-17"
}

Three ways in.

01

The desk

Feed, watchlists, conviction and company views — the whole universe, structured and searchable.

02

The REST API

Versioned endpoints under /api/v1. Clean JSON, documented, rate-limited, keyed.

03

The MCP server

One command connects the data layer to Claude, Cursor and ChatGPT.

Put the filing universe behind your code.