serpgrab: Google Search and Maps

com.serpgrab/google-searchserpgrab.comstreamable-httpv0.1.2Scanned 2 hours ago

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

2 tools: 2 only read.

Reads private data · 0
Reads text others write · 2
Can send data out · 0
No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Looks things up and changes nothing.Show 2 read-only tools

google_maps_searchBusinesses and places from Google Maps, 20 per page: name, type, rating and review count, price, address, phone, hours, website, coordinates and place_id.Reads text others writeNo findings
Why it is in this group
- The name "google_maps_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
google_searchReal-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 sho…Reads text others writeNo findings
Why it is in this group
- The name "google_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; google_maps_search
google_search
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Oct 22, 2026, 14:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 401
tools/list served without credentials: no
Tools that change things, listed without credentials: 0
Protocol version: not observed
WWW-Authenticate on 401: no
resource_metadata in WWW-Authenticate: not observed
RFC 9728 protected resource metadata: not observed
Authorization servers: not observed
Legacy HTTP+SSE transport: no
Dynamic client registration: not observed
Client ID metadata documents: not observed

WarnThe whole server
The endpoint asks for credentials (HTTP 401) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.
Matched text
https://api.serpgrab.com/mcp: initialize answered HTTP 401, without a WWW-Authenticate header
What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 0.1.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http google-search https://api.serpgrab.com/mcp --header 'X-API-Key: <your-x-api-key>'

claude mcp add --transport http google-search https://api.serpgrab.com/mcp --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__google-search__google_search",
      "mcp__google-search__google_maps_search"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as google-search. Review it before you use it.

Capability tags behind 2 rules

mcp__google-search__google_search untrusted-input
mcp__google-search__google_maps_search untrusted-input

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.serpgrab/google-search/verify?hash=b024974a4b2439afab099e2fd28b724e889185e36853c925cc6b86e937d1958e" | jq -e '.changed == false'

Pinned hash b024974a4b24, from Oct 24, 2026, 23:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.serpgrab/google-search/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/com.serpgrab/google-search.svg)](https://anlyon.dev/servers/com.serpgrab/google-search)

Source: MCP Registry · repository. Synced Oct 24, 2026, 23:17 UTC.