Google Maps data for agents
REMOTE · GOOGLE-MAPS.FETCHER.SH · SCANNED SEP 20
4 Google Maps endpoints. Pay per call in USDC via x402.
Available components
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 505 tokens (~84/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management48
- Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the Google Maps data for agents MCP server?
Google Maps data for agents is a hosted endpoint at https://google-maps.fetcher.sh/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 · google-maps.fetcher.sh
claude mcp add --transport http sh-fetcher-google-maps-mcp 'https://google-maps.fetcher.sh/mcp'
{
"mcpServers": {
"sh-fetcher-google-maps-mcp": {
"url": "https://google-maps.fetcher.sh/mcp"
}
}
} {
"servers": {
"sh-fetcher-google-maps-mcp": {
"type": "http",
"url": "https://google-maps.fetcher.sh/mcp"
}
}
} [mcp_servers.sh-fetcher-google-maps-mcp] url = "https://google-maps.fetcher.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-fetcher-google-maps-mcp": {
"type": "remote",
"url": "https://google-maps.fetcher.sh/mcp",
"enabled": true
}
}
} openclaw mcp add sh-fetcher-google-maps-mcp --url 'https://google-maps.fetcher.sh/mcp' --transport streamable-http
mcp_servers:
sh-fetcher-google-maps-mcp:
url: "https://google-maps.fetcher.sh/mcp" {
"McpServers": {
"sh-fetcher-google-maps-mcp": {
"Transport": "http",
"Url": "https://google-maps.fetcher.sh/mcp"
}
}
} assistant mcp add sh-fetcher-google-maps-mcp -t streamable-http -u 'https://google-maps.fetcher.sh/mcp'
{
"mcpServers": {
"sh-fetcher-google-maps-mcp": {
"type": "http",
"url": "https://google-maps.fetcher.sh/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Sept 26 −8
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “describe_endpoint” was removed ▼ security
- Tool “fetch_data” was removed ▼ security
- Tool “search_endpoints” was removed ▼ security
- New tool “google_maps_place” functional
- New tool “google_maps_place_reviews” functional
- New tool “google_maps_review” functional
- 6 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 73
- Tool “fetch_data” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
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 20 Sept 2026 · Probed https://google-maps.fetcher.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=google-maps.fetcher.sh | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9a8174ea0993d8913b49db476349734 |
| SANs: google-maps.fetcher.sh | ||||||
| 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 secure
Validation of google-maps.fetcher.sh. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| fetcher.sh. | present | 2371 | 13 | Verified |
| google-maps.fetcher.sh. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://google-maps.fetcher.sh/mcp | Verified | 200 | |
| http (plaintext) | http://google-maps.fetcher.sh/mcp | HTTPS enforced | 301 | https://google-maps.fetcher.sh/mcp |
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 →
check_balance ~37
Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
google_maps_place ~72
Paid ($0.005). Place — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | Optional. |
| fid | string | yes | Required. Path parameter. |
| languageCode | string | – | Optional. |
No output schema declared.
No examples provided.
google_maps_place_reviews ~101
Paid ($0.005). Place reviews — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | Optional. |
| cursor | string | – | Optional. |
| fid | string | yes | Required. Path parameter. |
| languageCode | string | – | Optional. |
| sort | string | – | Optional. One of: relevant, newest, highest, lowest. |
No output schema declared.
No examples provided.
google_maps_place_search ~103
Paid ($0.005). Place search — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | Optional. |
| languageCode | string | – | Optional. |
| latitude | string | – | Optional. |
| longitude | string | – | Optional. |
| offset | string | – | Optional. |
| query | string | yes | Required. |
| zoom | string | – | Optional. |
No output schema declared.
No examples provided.
google_maps_review ~54
Paid ($0.005). Review — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
topup_credits ~138
Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to add, in USD. Minimum 1. |
| rotate | boolean | – | Mint a replacement key for the paying wallet, invalidating the old one immediately. Only valid when no Authorization header is sent. |
No output schema declared.
No examples provided.
What is the Google Maps data for agents MCP server?
Google Maps data for agents is an MCP server listed in the public MCP registry as sh.fetcher.google-maps/mcp. 4 Google Maps endpoints. Pay per call in USDC via x402. This page covers its hosted endpoint (https://google-maps.fetcher.sh/mcp).
Is the Google Maps data for agents MCP server safe to use?
Google Maps data for agents scores 72 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 Maps data for agents MCP server expose?
Google Maps data for agents exposes 6 tools: google_maps_place_search, google_maps_place, google_maps_place_reviews, google_maps_review, check_balance, topup_credits. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.
Does the Google Maps data for agents MCP server require authentication?
No. We connected to Google Maps data for agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Google Maps data for agents MCP server still maintained?
Google Maps data for agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.