Gemini DeepSearch MCP - Automated research agent with Google Gemini models
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"gemini-deepsearch-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Gemini DeepSearch MCP Gemini DeepSearch MCP is an automated research agent that leverages Google Gemini models and Google Search to perform deep, multi-step web research. It generates sophisticated queries, synthesizes information from search results, identifies knowledge gaps, and produces high-quality, citation-rich answers. ## Features - **Automated multi-step research** using Gemini models and Google Search - **FastMCP integration** for both HTTP API and stdio deployment - **Configurable effort levels** (low, medium, high) for research depth - **Citation-rich responses** with source tracking - **LangGraph-powered workflow** with state management ## Usage ### Development Server (HTTP + Studio UI) Start the LangGraph development server with Studio UI: ```bash make dev ``` ### Local MCP Server (stdio) Start the MCP server with stdio transport for integration with MCP clients: ```bash make local ``` ### Testing Run the test suite: ```bash make test ``` Test the MCP stdio server: ```bash make test_mcp ``` Use MCP inspector ```bash make inspect ``` With Langsmith tracing ```bash GEMINI_API_KEY=AI******* LANGSMITH_API_KEY=ls******* LANGSMITH_TRACING=true make inspect ``` ## API The `deep_search` tool accepts: - **query** (string): The research question or topic to investigate - **effort** (string): Research effort level - "low", "medium", or "high" - **Low**: 1 query, 1 loop, Flash model - **Medium**: 3 queries, 2 loops, Flash model - **High**: 5 queries, 3 loops, Pro model ### Return Format **HTTP MCP Server** (Development mode): - **answer**: Comprehensive research response with citations - **sources**: List of source URLs used in research **Stdio MCP Server** (Claude Desktop integration): - **file_path**: Path to a JSON file containing the research results The stdio MCP server writes results to a JSON file in the system temp directory to optimize token usage. The JSON file contains the same `answer` and `sources` data as the HTTP version, …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.