Data · Remote MCP server
Google Search data for agents
1 Google Search endpoints. Pay per call in USDC via x402.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
sh.fetcher.google/mcp- Version
- 1.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-08-02
- Updated
- 2026-08-02
- Publisher
- sh.fetcher.google
- Namespace
- Namespace verified by the MCP Registry via the domain google.fetcher.sh or a parent domain of it · how
- Listed under
- Google Search MCP servers
- Website
- google.fetcher.sh
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://google.fetcher.sh/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- fetcher.sh - Google Search 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
google_search,check_balance,topup_credits - Checked on
- 2026-10-05
How to connect Google Search data for agents
Google Search data for agents is a remote MCP server: there is nothing to install. Its endpoint is https://google.fetcher.sh/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Google Search ConsoleGoogle Search Console: 37 tools, every API endpoint, hourly data, history beyond 16 months. | Local · stdio |
| Google Search ConsoleMCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection. | Local · stdio |
| Google Search Console MCPMCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites. | Local · stdio |
| Google Search Console MCPRead-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools. | Local · stdio |
| Google Surf MCPWeb, academic and code search with graph RAG, data lineage, ontology and cross-project schema links. | Local · stdio |
| Google Trends (via Apify)Google Trends data for AI agents: interest over time, regions, rising queries and trending searches. | Remote · HTTPLive check: sign-in required |
| Google Trends APIGoogle Trends search interest over time with growth metrics. Free key at trendsapi.ai. | Remote · HTTPLive check: ✓ handshake |
| Google Trends Scraper (orbots) - Apify ActorGoogle Trends trending searches, volume estimates & trend duration. Not affiliated with Google LLC. | Remote · HTTPLive check: sign-in required |