fetch_research_url — Claidex MCP MCP Tool Read-only
fetch_research_url
(fetch research url) is one of 24 tools on the
Claidex MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fetch_research_url from your client
- Claude Code Claidex MCP fetch_research_url run in your project directory
- Claude Desktop Claidex MCP fetch_research_url ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Claidex MCP fetch_research_url ~/.cursor/mcp.json
- VS Code Claidex MCP fetch_research_url .vscode/mcp.json
- Zed Claidex MCP fetch_research_url ~/.config/zed/settings.json
- Windsurf Claidex MCP fetch_research_url ~/.codeium/windsurf/mcp_config.json
- Cline Claidex MCP fetch_research_url ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Claidex MCP fetch_research_url ~/.gemini/settings.json
- Grok Claidex MCP fetch_research_url .mcp.json (in your project root)
- ChatGPT Claidex MCP fetch_research_url Settings → Connectors → Advanced → Developer mode
- Claude.ai Claidex MCP fetch_research_url Settings → Connectors → Add custom connector
- LangChain Claidex MCP fetch_research_url pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http failure-intelligence https://app.claidex.com/api/mcpOther tools on this server
- claidex_capabilities
- claidex_claim_risk_matrix
- claidex_health_snapshot
- claidex_research_prompt
- claidex_tool_catalog
- consult_specialist_model
- fetch
- get_claim_content
- query_chembl
- query_clinicaltrials
- query_failure_graph
- query_openfda
- query_opentargets
- query_package_registry
- rank_documents_by_embedding
- rerank_documents
- run_computation
- run_statistical_analysis
- search
- search_claims
- search_preprint_flags
- search_pubmed
- web_search
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.