serpgrab: Google Search and Maps
REMOTE · API.SERPGRAB.COM · 2 COMPONENTS
Real-time Google search (AI Overview, answer box, People also ask) and Google Maps places.
Available components
Last scanned (13 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 +40
- Transport: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 21 Oct 26 28
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.serpgrab.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=serpgrab.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 57fcac1a27bd6800e2568927d8c6082 |
| SANs: serpgrab.com, *.serpgrab.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.serpgrab.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| serpgrab.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.serpgrab.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.serpgrab.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
google_maps_search Google Maps search ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to look for, e.g. "pizza in austin tx". |
No output schema declared.
No examples provided.
google_search Google search ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The search, as typed into Google. |
| time | string | – | Only results from the past hour, day, week, month or year. |
No output schema declared.
No examples provided.
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.
remote · api.serpgrab.com
claude mcp add --transport http com-serpgrab-google-search 'https://api.serpgrab.com/mcp'
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.