Google Search data for agents MCP Server

by fetcher-google Your server? Claim it

answering

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

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

Uptime history 51 days of history · worst day 97%

51 days agonow

97.8%

Uptime 24h

89 of 91 checks

Tools

read from the server

417 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 30

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 August 2026. No other catalogue keeps this.

6 Sep 3 tools disappeared describe_endpoint, fetch_data, search_endpoints

5 Sep 10 tools appeared appstore_apps, google_maps_place_search, google_news_search and 7 more

5 Sep 10 tools disappeared appstore_apps, google_maps_place_search, google_news_search and 7 more

5 Sep 2 tools changed the parameters they ask for4 times that day fetch_data, search_endpoints

5 Sep 2 tool descriptions were rewritten fetch_data, search_endpoints

21 Aug a tool description was rewritten fetch_data

and 2 more, back to 21 August 2026

Google Search data for agents does not always answer

Over the last week it answered 98.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 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 3

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.

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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

appstore_apps

removed 5 Sep 2026

google_maps_place_search

removed 5 Sep 2026

google_news_search

removed 5 Sep 2026

googleplay_apps

removed 5 Sep 2026

instagram_user_handle

removed 5 Sep 2026

reddit_search_post

removed 5 Sep 2026

tiktok_post_search

removed 5 Sep 2026

twitter_search

removed 5 Sep 2026

yelp_search

removed 5 Sep 2026

youtube_search_video

removed 5 Sep 2026

describe_endpoint

removed 6 Sep 2026

fetch_data

removed 6 Sep 2026

search_endpoints

removed 6 Sep 2026

Endpoints

URL	Transport	State	Latency	Checked
https://google.fetcher.sh/mcp	streamable-http	answering	425 ms	4 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.

9 tools answering

Google News data for agents

by fetcher-google-news

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

14 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

Web Search & Data API

by kadec0

Web search, scraping, Google Trends and data lookups. Paid per call in USDC on Base via x402.

23 tools answering

Blockrun MCP

by blockrunai

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

653 installs/wk local only

Forage

by forage

Web search and URL-to-markdown for agents. Pay per call in USDC on Base, no signup.

2 tools answering

AgentIndex x402

by agentindex

Pay-per-call web search, translation and research jobs for AI agents. USDC on Base, no account.

18 tools answering

DexL Agents

by dexl-io

Pay-per-call AI gateway: models, speech, web search, on-chain reads and NLP tools, via x402.

5 tools 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 3 tools, read directly from the server on our last check. Among them: check_balance, google_search, 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 89 of 91 checks got a reply (97.8%), average response time 417 ms. The bar chart above shows every period we have measured.

Did Google Search data for agents ever remove tools?

Yes. appstore_apps, google_maps_place_search, google_news_search, googleplay_apps and 9 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

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 3 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 417 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.