MCP tools over Google Search through a dedicated logged-in browser profile: personalized organic results, ads stripped, the full advanced-operator surface, and pagination
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":"gsearch-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.
# google-search-mcp MCP tools over Google Search, through a dedicated logged-in browser profile. Personalized organic results, ads stripped, the full advanced-operator surface, and pagination. Published on PyPI as **`gsearch-mcp`** (`google-search-mcp` was already taken, by an unrelated Custom Search API wrapper). Import package and repo keep the longer name. Three-layer shape: all site knowledge in `client.py`, a CLI that mirrors the tools 1:1 as the debugging surface, and a thin MCP wrapper. ## Why this exists No official Google Search API serves this intent. The Custom Search JSON API returns results from a *configured subset* of the web with no personalization, is **closed to new customers**, and **sunsets 1 Jan 2027**. That is a §0 Q1 negative on all three sub-questions. What you get that a keyword search API does not: - **The advanced-operator surface** — `site:`, `filetype:`, exact phrase, exclusions, `before:`/`after:` bounds, freshness windows down to the **past hour**, **verbatim** (no synonyms or stemming), every Google vertical, region and language bias. All server-side, all free once the transport works. This is the strongest reason to use it; no keyword API has an equivalent. - **Better sources on technical queries.** Measured head-to-head against the harness `WebSearch` and the Brave API on `MCP stateless server migration`: this returned the Google and Cloudflare engineering blogs, the spec's own GitHub issue and the Spring docs, where both alternatives returned a page of SEO blogspam paraphrasing the same announcement. Full comparison in `docs/ROADMAP.md`. - **Personalized ranking.** Measured at **~3.4× the run-to-run noise floor**: disabling it moved roughly a third of the top-10. Qualitatively it resolves ambiguous technical queries toward the domain sense — `spring` returns Spring Framework rather than the film, `mcp server` returns Cloudflare's engineering blog rather than a content farm. Full method and caveats in …
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.