Google Search data for agents

Official registry Search and web

1 Google Search endpoints. Pay per call in USDC via x402.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http google-search-data-for-agents 'https://google.fetcher.sh/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "google-search-data-for-agents": {
            "type": "http",
            "url": "https://google.fetcher.sh/mcp"
        }
    }
}

Frequently asked questions

What is Google Search data for agents?

1 Google Search endpoints. Pay per call in USDC via x402.

How do I install Google Search data for agents?

It runs as a remote server. In Claude Code: claude mcp add --transport http google-search-data-for-agents 'https://google.fetcher.sh/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Google Search data for agents need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains Google Search data for agents?

It is published by sh.fetcher.google. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.