mcpbeat Sign in

Deep Research MCP Server

answering

Deep Research is answering right now. Last checked 10 min ago.

Autonomous buy-side research: diligence, earnings, SEC filings, comp sets. Source-cited real data.

Uptime history 90 days of history · worst day 64%
90 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
236 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Deep Research every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add deep-research --transport http https://mcp.openhelm.ai/research/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.openhelm.ai/research/mcp
~/.codex/config.toml
[mcp_servers.deep-research]
url = "https://mcp.openhelm.ai/research/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "deep-research": {
      "url": "https://mcp.openhelm.ai/research/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "deep-research": {
      "type": "http",
      "url": "https://mcp.openhelm.ai/research/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.openhelm.ai/research/mcp streamable-http sign-in 265 ms 10 min ago

Alternatives to Deep Research

same job, measured the same way
Financial Evidence Workspace
by beepboop2025

Read-only cited financial datasets, bounded research queries and source diagnostics.

12 tools answering
SEC Filings
by tributarydata

Official SEC EDGAR filings, financial data and full-text search. Every answer cites its source.

answering
RCQ Data Oracle
by rcqsignals

Signed BTC and macro market intelligence for autonomous research, risk, and trading agents.

7 tools answering
FactIQ
by factiq

Official economic statistics, company filings, earnings calls and market data, with sources cited.

answering
SEC EDGAR Financial Data
by taru0208

Search SEC EDGAR filings, financial statements, and company data.

answering
S
SEC Filings & Earnings
by memoryapi

SEC filings, insider trades, and earnings data

5 tools answering
Bigdata.com
by bigdata

Licensed, cited financial data for AI agents: news, filings, transcripts, research and tearsheets.

answering
India Company & Director Data
by thecompanyatlas

Indian company registry research and director-related company due diligence.

answering

Deep Research — questions

Answers built from our own checks of this server.

Why is there no tool list for Deep Research?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Deep Research working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 236 ms. The bar chart above shows every period we have measured.
How do I connect Deep Research?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Deep Research?
No API key is involved. Deep Research answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Deep Research?
It answers our handshake in 236 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.