Google Researcher

io.github.zoharbabinPublished by GitHub account zoharbabinv6.3.3Updated Oct 24, 2026

MCP server providing Google Search, web scraping, and multi-source research tools for AI assistants

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

Deprecated local MCP server that gave assistants Google Search, web scraping and multi-source research tools; superseded by web-researcher-mcp.

What you can do
  • Search the web through Google Programmable Search using a configured API key and search engine ID.
  • Scrape and extract content from web pages for research.
  • Combine several sources into multi-source research results.
  • The README lists no individual tool names and states the project is deprecated in favour of a Go rewrite with the same tools.
When to use it
Only if you already depend on this package or need a Node-based Google search and scraping server. New setups should use the successor project instead, since this one is marked deprecated and its tool names collide with the replacement.
Requirements
Runs locally over stdio as an npm package launched with node (for example via npx). Requires a Google Custom Search API key in GOOGLE_CUSTOM_SEARCH_API_KEY and a Programmable Search Engine ID in GOOGLE_CUSTOM_SEARCH_ID. Network access to Google and to scraped sites. Desktop only.
Before you install
The project is deprecated and superseded; the README says not to run it alongside the replacement because both register identical tool names. It needs a Google API key, which may incur Google quota or billing. Scraping sends requests to third-party sites. The README's migration steps include shell install scripts; review them before running.

Installation

In SourceWeft

  1. Open Google Researcher in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

google-researcher-mcp — DEPRECATED

⚠️ This project has been superseded by web-researcher-mcp.

A complete rewrite in Go: same tools, but it cites real sources and stays honest — citation verification, retraction flagging, eight search providers behind one interface, and a single signed static binary. No Node.js, no npm.

Migrate in one line

Your API keys and tool calls don't change — only how the server is launched. Pick whichever you prefer (no Node required):

bash
# macOS / Linux — installs the binary and registers it with Claude Code automatically:curl -fsSL https://raw.githubusercontent.com/zoharbabin/web-researcher-mcp/main/install.sh | sh
# Windows (PowerShell):powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/zoharbabin/web-researcher-mcp/main/install.ps1 | iex"
# Python users (uv) — run with no install:uvx web-researcher-mcp

Before / after (MCP client config)

The config keeps the same shape — swap the command/args, keep your env:

jsonc
// BEFORE — google-researcher-mcp (npx / Node){  "mcpServers": {    "google-researcher": {      "command": "npx",      "args": ["-y", "google-researcher-mcp"],      "env": { "GOOGLE_CUSTOM_SEARCH_API_KEY": "…", "GOOGLE_CUSTOM_SEARCH_ID": "…" }    }  }}
// AFTER — web-researcher-mcp (installed binary; or use "uvx" + args ["web-researcher-mcp"]){  "mcpServers": {    "web-researcher": {      "command": "web-researcher-mcp",      "env": { "GOOGLE_CUSTOM_SEARCH_API_KEY": "…", "GOOGLE_CUSTOM_SEARCH_ID": "…" }    }  }}

Don't run both at once — they register identical tool names. Remove the google-researcher entry before adding web-researcher.

→ Full migration guide

Your existing GOOGLE_CUSTOM_SEARCH_API_KEY and GOOGLE_CUSTOM_SEARCH_ID work unchanged.

Why the Rewrite?

Open IssueResolution in web-researcher-mcp
#108 — Orphan detection fails via npxGo binary has native process lifecycle (EOF/SIGPIPE) — no npm wrapper
#107 — Google discontinuing 'entire web' searchEight providers (Brave, Serper, SearXNG, SearchAPI, Tavily, Exa, DuckDuckGo + Google PSE for lenses) with automatic fallback
#55 — Support alternative search enginesMultiple engines behind one interface, plus a zero-config DuckDuckGo default
#72 — Add Redis cachingHybrid cache: memory + AES-encrypted disk + optional Redis
#40 — Split server.ts into modulesFully modular Go architecture (one package per concern)

Plus what's new: verify_citation and audit_bibliography (catch fabricated/retracted citations), academic / patent / SEC-filing / US-case-law / economic / clinical-trial search, and authority-weighted search lenses.

Links

Source: README.md at commit bad0569

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v6.3.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts