io.github.zoharbabin/google-researcher

MCPcommunity
v6.3.3io.github.zoharbabinUnknownUpdated 1mo agonpmGitHub

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

⚠️ This project has been superseded by . The new version is a complete rewrite in Go that resolves all open issues, adds multiple search providers (Brave, Serper, SearXNG), and ships as a single static binary — no Node.js or npm required. → Full migration instructions 1. Remove the entry from your MCP client config 2. Install the new binary (, Docker, or download from Releases) 3. Add the entry…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.zoharbabin
LicenseUnknown
Version6.3.3
Sourcemcp-registry
npmgoogle-researcher-mcp
GitHubzoharbabin/google-researcher-mcp
Trust Status
A
95/100Trusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
✓npm provenance (Sigstore)+5/5
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · eef00cd
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv7.0.0 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

⚠️ This project has been superseded by . The new version is a complete rewrite in Go that resolves all open issues, adds multiple search providers (Brave, Serper, SearXNG), and ships as a single static binary — no Node.js or npm required. → Full migration instructions 1. Remove the entry from your MCP client config 2. Install the new binary (, Docker, or download from Releases) 3. Add the entry to your MCP config Your existing and work without changes. Open Issue | Resolution in…

Keywords
mcp