Remote MCP · Endpoint

Google Search data for agents MCP server

No. Google Search data for agents answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://google.fetcher.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.fetcher.google/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
116 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
1 Google Search endpoints. Pay per call in USDC via x402.
Website
https://google.fetcher.sh/
Listing
From the official MCP registry (active).
Recent checks of Google Search data for agents
CheckedResultHandshake
1 hour agoHandshake completed116 ms
2 days agoHandshake completed126 ms
4 days agoHandshake completed169 ms
5 days agoHandshake completed88 ms
7 days agoHandshake completed116 ms
8 days agoHandshake completed106 ms
9 days agoHandshake completed598 ms
12 days agoHandshake completed94 ms
13 days agoHandshake completed98 ms
15 days agoHandshake completed86 ms
16 days agoHandshake completed102 ms
18 days agoHandshake completed89 ms
19 days agoHandshake completed133 ms
20 days agoHandshake completed115 ms
21 days agoHandshake completed72 ms
21 days agoHandshake completed102 ms
23 days agoHandshake completed79 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Google Search data for agents and makes no claim about it beyond what these checks measured.