# Google Search MCP (remote · mcp.wondel.ai)

Fast Google web search: organic results and related questions, no ads.

- Trust score: 55/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.wondel.ai`: 55/100 (this document), [markdown](https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp.md), [page](https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp)

## Channel facts

- Endpoint: `https://mcp.wondel.ai/google-search/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 42/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 606 tokens (~606/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Google Search MCP server?

Google Search MCP is a hosted endpoint at https://mcp.wondel.ai/google-search/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-wondel-google-search 'https://mcp.wondel.ai/google-search/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-wondel-google-search": {
      "url": "https://mcp.wondel.ai/google-search/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-wondel-google-search": {
      "type": "http",
      "url": "https://mcp.wondel.ai/google-search/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-wondel-google-search]
url = "https://mcp.wondel.ai/google-search/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-wondel-google-search": {
      "type": "remote",
      "url": "https://mcp.wondel.ai/google-search/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-wondel-google-search --url 'https://mcp.wondel.ai/google-search/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-wondel-google-search:
    url: "https://mcp.wondel.ai/google-search/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-wondel-google-search": {
      "Transport": "http",
      "Url": "https://mcp.wondel.ai/google-search/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-wondel-google-search -t streamable-http -u 'https://mcp.wondel.ai/google-search/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-wondel-google-search": {
      "type": "http",
      "url": "https://mcp.wondel.ai/google-search/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 54, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 54)

First indexed and scored.

## MCP tools (1)

### `google_search` (~506 tokens)

Search Google (SerpAPI)

Fast Google web search via SerpAPI's google_light engine. Returns organic_results, related_questions and related_searches (lighter and faster than the full Google engine; no ads, inline images or other rich elements). Paginate with start (+10 results per page: 0, 10, 20, …). Localize with location or uule (mutually exclusive), gl/hl for country/language, and lr to restrict result languages.

Input parameters:

- `device` (string): Device to emulate for the search: 'desktop' (default), 'tablet' or 'mobile'.
- `filter` (integer): 'Similar Results' and 'Omitted Results' filter: 1 = on (default), 0 = off (show all).
- `gl` (string): Country code for the search, e.g. 'us', 'uk', 'de'.
- `google_domain` (string): Google domain to use, e.g. 'google.com', 'google.co.uk', 'google.de'. Default google.com.
- `hl` (string): Language code, e.g. 'en', 'es', 'fr'.
- `location` (string): Geographic location to originate the search from, e.g. 'Austin, Texas, United States'. Mutually exclusive with uule.
- `lr` (string): Restrict results to one or more languages, e.g. 'lang_en' or 'lang_en|lang_fr'.
- `nfpr` (integer): Exclude auto-corrected (spelling-fix) results: 1 = exclude (use the exact query), 0 = allow (default).
- `no_cache` (boolean): Force a fresh SerpAPI fetch and bypass this server's result cache. Default false.
- `q` (string, required): Search query / keywords (required). Supports standard Google operators (site:, intitle:, quotes, …).
- `safe` (string): SafeSearch level: 'active' to filter explicit results, 'off' to disable.
- `start` (integer): Result offset for pagination (0-based): 0 = page 1, 10 = page 2, 20 = page 3, … (+10 per page).
- `uule` (string): Google-encoded location string (uule); advanced alternative to location. Mutually exclusive with location.
- `zero_trace` (boolean): Enterprise-only ZeroTrace mode: don't store search params/metadata on SerpAPI. Default false.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp#diagnostics

## Score history

- 2026-11-05: 55
- 2026-11-04: 55
- 2026-11-03: 54
- 2026-11-02: 54

## Common questions

### What is the Google Search MCP server?

Google Search MCP is listed in the public MCP registry as ai.wondel/google-search. Fast Google web search: organic results and related questions, no ads. This page covers its hosted endpoint (https://mcp.wondel.ai/google-search/mcp).

### Is the Google Search MCP server safe to use?

Google Search MCP scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Google Search MCP server expose?

Google Search MCP exposes 1 tool: google_search. Their descriptions and schemas cost roughly 506 tokens of context every time the server is loaded.

### Does the Google Search MCP server require authentication?

No. We connected to Google Search MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Google Search MCP server still maintained?

Google Search MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Google Search MCP server?

VerifyMCP ran 11 checks on Google Search MCP, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Google Search MCP: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.wondel.ai/google-search/mcp
- Website: https://mcps.wondel.ai/servers/google-search/
- Changelog RSS feed: https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-wondel-google-search/google-search-mcp