GPT Researcher
GPT Researcher is an MCP client published by Assaf Elovic; its MCP spec-revision support has not been verified yet. Last verified 2026-09-15.
Does GPT Researcher support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision GPT Researcher supports (as of 2026-09-15).
Which MCP client features does GPT Researcher support?
GPT Researcher supports: tools (last verified 2026-09-15).
When were GPT Researcher's facts last verified?
2026-09-15. Each fact on this page links to the sources used to verify it.
GPT Researcher is an open-source research agent maintained by Assaf Elovic
that produces research reports with citations from web and local sources.
Its MCP client surface is opt-in: setting the RETRIEVER environment
variable to mcp (or a hybrid value such as tavily,mcp) activates a
retriever that reads a list of mcp_configs dictionaries, each naming a
server by name plus either a command and args pair for a local stdio
subprocess, the default when no connection URL is given, or a
connection_url for a remote server whose scheme selects a websocket or
streamable HTTP transport. The dependency floor is mcp>=1.9.1 and
langchain-mcp-adapters>=0.1.0, and the client code calls the latter
library's MultiServerMCPClient rather than the mcp SDK directly. Only
the tools feature is documented or implemented: the retriever selects
relevant tools across configured servers with an LLM step, then calls them
with generated arguments. No resources, prompts, sampling, elicitation, or
roots handling appears in the client code or documentation, and no project
surface names an MCP specification revision, so spec status is recorded as
unknown.
As of 2026-09-15 the project carries three disagreeing version numbers: the
PyPI package reports 0.16.0, the pyproject.toml on the main branch
declares 0.15.1 in both its legacy Poetry block and its modern project
block, and the newest GitHub tag is v3.6.1, a separate numbering line
altogether. None of the three matches v0.14.8, the version
CVE-2026-37006 named as the
fix for an unauthenticated WebSocket configuration flaw, a discrepancy the
published story already flagged and this pass confirms extends across all
three surfaces. The package ships as a pip install, a Docker image
(gptresearcher/gpt-researcher on Docker Hub), and a self-hosted web
frontend served by FastAPI with an optional Next.js build. The project's
SECURITY.md documents the MCP configuration surface as an operator-trust
boundary, stating that accepting MCP server commands from an authenticated
operator is an intended feature and that exposing the endpoint to
untrusted clients falls outside the project's threat model.
How was this verified, and what are the sources?
Verified · method: repo-readme
· confidence 0.85 (Good).
- docs.gptr.dev MCP configuration guide, fetched 2026-09-15, cross-checked against the identical in-repo file - "Each MCP configuration dictionary supports these keys: name ... command ... args ... env ... connection_url ... connection_type ... connection_token. Local servers: Require name, command, and args. Remote servers: Require name and connection_url"; connection type auto-detected from the URL scheme (wss:// -> websocket, https:// or http:// -> streamable_http, no URL -> stdio); enabling MCP requires setting RETRIEVER=mcp - accessed
- gpt_researcher/mcp/client.py, fetched 2026-09-15 - convert_configs_to_langchain_format maps a wss/ws prefix to transport "websocket", an https/http prefix to "streamable_http", and otherwise defaults connection_type to "stdio"; imports MultiServerMCPClient from langchain_mcp_adapters.client and exposes get_all_tools() calling client.get_tools(); no reference to resources, prompts, sampling, elicitation, or roots anywhere in the module - accessed
- requirements.txt, fetched 2026-09-15 - "# MCP Support (optional)" then exact lines "mcp>=1.9.1" and "langchain-mcp-adapters>=0.1.0" - accessed
- GitHub repository assafelovic/gpt-researcher via the GitHub API, fetched 2026-09-15 - 29,461 stars, owner.type "User" (login assafelovic, not an organization), homepage https://gptr.dev, license Apache-2.0, topics include mcp and mcp-server - accessed
- PyPI registry metadata for gpt-researcher, fetched 2026-09-15 - info.version 0.16.0, uploaded 2026-07-18; pyproject.toml on the main branch (fetched the same day) instead declares version "0.15.1" in both its [tool.poetry] and [project] blocks, and the newest GitHub tag is v3.6.1 (published 2026-08-24) - three disagreeing version numbers across PyPI, the default branch, and tags - accessed
- SECURITY.md, fetched 2026-09-15 - "The backend server (FastAPI + WebSocket, /ws and the REST endpoints) ships without built-in authentication or network access controls, by design," and names "Remote code execution via user-supplied MCP command/args" as an operator-configuration concern out of scope as a project vulnerability, since "configuring MCP servers is an intended feature for the trusted operator" - accessed