Google Search data for agents MCP Server

by fetcher-google

answering

Google Search data for agents is answering right now. Last checked 5 min ago. It exposes 6 tools.

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

Uptime history 55 hours of history

55 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

480 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://google.fetcher.sh/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://google.fetcher.sh/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://google.fetcher.sh/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://google.fetcher.sh/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://google.fetcher.sh/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

balance

check_balance

Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.

data

fetch_data

Paid. Fetch live data from any Google Search endpoint. Pass the endpoint path plus its parameters (path and query parameters together in `params`). Priced per call in USDC on Base, Polygon, Arbitrum, Monad or Solana: pay with x402, or send an Authorization: Bearer bby_live_... header to spend prepaid credits. Call describe_endpoint first if unsure about parameters.

describe

describe_endpoint

Free. Show the full call signature for one endpoint: required and optional parameters, allowed values, price, and response shape.

endpoints

search_endpoints

Free. Search fetcher.sh's Google Search endpoints by keyword. Returns paths, descriptions and per-call prices. Start here.

google

google_search

Paid ($0.005). Search — Google Search. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

topup

topup_credits

Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.

Endpoints

URL	Transport	State	Latency	Checked
https://google.fetcher.sh/mcp	streamable-http	answering	546 ms	5 min ago

Alternatives to Google Search data for agents

same job, measured the same way

Google Play data for agents

by fetcher-googleplay

7 Google Play endpoints. Pay per call in USDC via x402.

6 tools answering

Google News data for agents

by fetcher-google-news

12 Google News endpoints. Pay per call in USDC via x402.

6 tools answering

Google Maps data for agents

by fetcher-google-maps

4 Google Maps endpoints. Pay per call in USDC via x402.

6 tools answering

Blockrun MCP

by blockrunai

Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.

1 170 installs/wk local only

Gnosis Memory

by gnosismemory

Persistent memory and vector search for AI agents. Hosted, OAuth-protected via Google sign-in.

answering

Pa1m SEO

by retampweb

Pay-per-call SEO agent: keyword research, SERP analysis, on-page optimization. x402, USDC on Base.

36 tools answering

Taskfleet MCP

by bfai-1

Pay-per-call MCP tools: web search, scraping, on-chain wallet intel, extraction. x402 USDC on Base.

124 installs/wk local only

MCP Serp

by acedatacloud

MCP server for Google search results via SERP API

949 installs/wk answering

Google Search data for agents — questions

Answers built from our own checks of this server.

What can Google Search data for agents do?

It exposes 6 tools, read directly from the server on our last check. Among them: check_balance, describe_endpoint, fetch_data, google_search, search_endpoints, topup_credits. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Google Search data for agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 480 ms. The bar chart above shows every period we have measured.

How do I connect Google Search data for agents?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Google Search data for agents need an API key?

No. Google Search data for agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Google Search data for agents?

It answers our handshake in 480 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.