mcp-registry/ai.fodda/deep-research · v1.46.126
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 68 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.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 124 ms | 83% of MCP servers |
| p95 handshake latency | 443 ms | — |
| Checks in 30 days | 224 | — |
| Outages, 90 days | 68 | — |
| 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 | — |
As of 2026-10-27 03:29 UTC, the Fodda Deep Research MCP server is up (it requires sign-in) with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 67 outages in 90 days, with a median recovery of 2 minutes.
Autonomous deep research reports merging PSFK trend graphs with citable sources.
Claude Code
claude mcp add --transport http fodda-deep-research-mcp-server https://mcp.fodda.ai/deep-research
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"fodda-deep-research-mcp-server": {
"type": "http",
"url": "https://mcp.fodda.ai/deep-research"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
In the last 30 days: 0 tool(s) removed and 6 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.fodda/deep-research"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.fodda/deep-research"}) over MCP.
search_graph ~818 tokensget_supplemental_context ~558 tokensget_neighbors ~556 tokensdeep_research_topic ~514 tokensget_evidence ~440 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.fodda%2Fdeep-research?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.fodda%2Fdeep-research?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.fodda%2Fdeep-research.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.fodda%2Fdeep-research.svg :target: https://glimind.com/server/mcp-registry%2Fai.fodda%2Fdeep-research?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fc3d9679413e777e…, first seen 2026-10-23, included at leaf 52784 of 77,139. Version history · verify what your client received.
Compare: most reliable research servers · most reliable data servers · most reliable media servers · most reliable knowledge servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:29 UTC, the Fodda Deep Research MCP server is up (it requires sign-in) with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 67 outages in 90 days, with a median recovery of 2 minutes.
Fodda Deep Research MCP server advertises 14 tools, including check_research_status, check_supplemental_status, deep_research_topic, generate_visual, get_capabilities.
Point your MCP client at this streamable-http endpoint: https://mcp.fodda.ai/deep-research
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.