# serpgrab: Google Search and Maps (remote · api.serpgrab.com)

Real-time Google search (AI Overview, answer box, People also ask) and Google Maps places.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.serpgrab.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-serpgrab-google-search/api.md), [page](https://verifymcp.io/servers/com-serpgrab-google-search/api)
- remote · `google-serp-search-results-json.p.rapidapi.com`: 23/100, [markdown](https://verifymcp.io/servers/com-serpgrab-google-search/google-serp-search-results-json.md), [page](https://verifymcp.io/servers/com-serpgrab-google-search/google-serp-search-results-json)

## Channel facts

- Endpoint: `https://api.serpgrab.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.1.2`

## 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**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 455 tokens (~227/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 2 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the serpgrab: Google Search and Maps MCP server?

serpgrab: Google Search and Maps is a hosted endpoint at https://api.serpgrab.com/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 com-serpgrab-google-search 'https://api.serpgrab.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-serpgrab-google-search": {
      "url": "https://api.serpgrab.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-serpgrab-google-search": {
      "type": "http",
      "url": "https://api.serpgrab.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-serpgrab-google-search]
url = "https://api.serpgrab.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-serpgrab-google-search --url 'https://api.serpgrab.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-serpgrab-google-search:
    url: "https://api.serpgrab.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-serpgrab-google-search": {
      "Transport": "http",
      "Url": "https://api.serpgrab.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-serpgrab-google-search -t streamable-http -u 'https://api.serpgrab.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-serpgrab-google-search": {
      "type": "http",
      "url": "https://api.serpgrab.com/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-05 (score 74, +1)

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

### 2026-11-03 (score 73, +1)

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

### 2026-10-31 (score 72, +1)

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

### 2026-10-29 (score 71, +1)

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

### 2026-10-27 (score 70, +1)

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

### 2026-10-25 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 68, +40)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-10-21 (score 28)

First indexed and scored.

## MCP tools (2)

### `google_search` (~251 tokens)

Google search

Real-time Google web results: title, URL, date and snippet for each result, plus the AI Overview, answer box, knowledge panel, local pack, ads and "People also ask" when Google shows them. Question-style queries ("how do I...", "what is...") usually get an AI Overview. Each page read is one billed search, so use pages=1 unless you need more. Usually 2-6 s per page.

Input parameters:

- `country` (string): Two-letter country code Google searches from (gl), e.g. "us", "gb", "de". Default "us".
- `language` (string): Interface language (hl), e.g. "en", "de", "pt-BR". Default "en".
- `location` (string): Search as if from this place, e.g. "Austin, Texas, United States". Leave out for a country-wide search.
- `pages` (integer): Result pages to read (about 10 results each), 1-3. Default 1.
- `query` (string, required): The search, as typed into Google.
- `time` (string): Only results from the past hour, day, week, month or year.

### `google_maps_search` (~204 tokens)

Google Maps search

Businesses and places from Google Maps, 20 per page: name, type, rating and review count, price, address, phone, hours, website, coordinates and place_id. Put the place in the query ("plumber in denver co") or pass ll. Each page is one billed search.

Input parameters:

- `country` (string): Two-letter country code Google searches from (gl), e.g. "us", "gb", "de". Default "us".
- `language` (string): Interface language (hl), e.g. "en", "de", "pt-BR". Default "en".
- `ll` (string): Map position as "@latitude,longitude,zoomz", e.g. "@30.2672,-97.7431,14z".
- `page` (integer): Results page, 20 places each. Default 1.
- `query` (string, required): What to look for, e.g. "pizza in austin tx".

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 68
- 2026-10-23: 28
- 2026-10-22: 28
- 2026-10-21: 28

## Common questions

### What is the serpgrab: Google Search and Maps MCP server?

serpgrab: Google Search and Maps is an MCP server listed in the public MCP registry as com.serpgrab/google-search. Real-time Google search (AI Overview, answer box, People also ask) and Google Maps places. This page covers its hosted endpoint (https://api.serpgrab.com/mcp).

### Is the serpgrab: Google Search and Maps MCP server safe to use?

serpgrab: Google Search and Maps scores 74 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 serpgrab: Google Search and Maps MCP server expose?

serpgrab: Google Search and Maps exposes 2 tools: google_search, google_maps_search. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.

### Does the serpgrab: Google Search and Maps MCP server require authentication?

Yes. serpgrab: Google Search and Maps asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the serpgrab: Google Search and Maps MCP server still maintained?

serpgrab: Google Search and Maps 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.

## Links

- Remote endpoint: https://api.serpgrab.com/mcp
- Authorisation metadata: https://api.serpgrab.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/Fiery-Tools/serpgrab-mcp
- Website: https://serpgrab.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-serpgrab-google-search/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-serpgrab-google-search/api.json
- HTML version of this page: https://verifymcp.io/servers/com-serpgrab-google-search/api