# Fodda Deep Research MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.fodda%2Fdeep-research
Registry id: `mcp-registry/ai.fodda/deep-research`
Status: auth-required (checked 2026-10-27T04:30:35.835Z)

## Verdict

Fodda Deep Research MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 124 ms median handshake and 67 outages in 90 days. Its agent-readiness grade is A (94/100) across 14 tools, costing an agent about 5,276 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 124 ms | 83% of MCP servers |
| p95 handshake latency | 451 ms | — |
| Checks in 30 days | 227 | — |
| Outages, 90 days | 67 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 94/100 (A) | 78% of MCP servers |
| Tools | 14 | — |
| Tool-list size for an agent | ~5,276 tokens | 37% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "fodda-deep-research-mcp-server": {
      "type": "http",
      "url": "https://mcp.fodda.ai/deep-research"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http fodda-deep-research-mcp-server https://mcp.fodda.ai/deep-research
```

## Tools (14)

- `check_research_status`: Polling and retrieval layer for deep research jobs: checks execution status and retrieves the completed research briefing report. Call after initiating deep_res
- `check_supplemental_status`: Check if market data gathering is complete and retrieve the results. Call this after get_supplemental_context — poll every 5-10 seconds until status is COMPLETE
- `deep_research_topic`: Use when commissioning an autonomous multi-pass research report synthesizing cross-graph trends, corporate disclosures, and expert perspectives into a comprehen
- `generate_visual`: Create a presentation-ready data visualization from research findings. Available chart types: "cultural_shifts" (From→To transitions), "competitive_compass" (br
- `get_capabilities`: Returns Fodda's capabilities, semantic research workflows, Human Agents (Human Agents), and pricing. Call this for any question about what Fodda can do, how exp
- `get_evidence`: Evidence citation lookup: retrieves primary evidence articles, publisher case studies, data points, and source URLs that validate a specific trend node. Prerequ
- `get_label_values`: List unique taxonomy entity values (brands, locations, technologies, audiences) or retrieve the complete table of contents for small, discrete report graphs (<4
- `get_my_account`: Check the current user's account status: API call balance, plan, enabled/disabled graphs, and profile info. Use when the user asks "how many API calls do I have
- `get_neighbors`: Discover what's connected to a specific trend — related brands, technologies, locations, and cross-domain links. Returns curated editorial connections between t
- `get_node`: Get the full profile of a specific trend — detailed description, lifecycle stage (emerging/building/mature), signal strength, geographic scope, and all properti
- `get_supplemental_context`: Federated empirical data layer: queries 110+ live institutional and government feeds (FRED, BLS, US Census, World Bank, OECD, WTO, IMF PortWatch, etc.) for real
- `list_graphs`: Catalog and discovery layer for Fodda knowledge graphs: lists all accessible knowledge graph IDs, topic vertical tags, author credentials, node counts, and sign
- `read_url`: Extract clean text content from any URL. Use this when a user shares a link (competitor site, news article, client brief, trend report) and wants to cross-refer
- `search_graph`: Use when searching for market trends, category dynamics, and consumer shifts across 100+ curated knowledge graphs. Returns trends with cited evidence, lifecycle

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.