Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google Maps Places, Reviews & Local Leads API MCP Server

REMOTE · API.GOOGLEMAPSAPI.IO · 2 COMPONENTS

Real-time Google Maps local business leads, reviews, places & emails MCP. OAuth or API key.

0 this week 23 Trust /100

Last scanned (21 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 8 Nov 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 6 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 5 Nov 26 72

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.googlemapsapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=googlemapsapi.io CN=YE2,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 6e6f40d21b4b1eb9a439c89f6b51768366e
SANs: *.googlemapsapi.io, googlemapsapi.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.googlemapsapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
googlemapsapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 410

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.googlemapsapi.io/mcp HTTP error 410
http (plaintext) http://api.googlemapsapi.io/mcp HTTPS enforced 301 https://api.googlemapsapi.io/mcp
MCP tools · 8 exposed · ~1,066 tokens

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 →

Tool Tokens
geocode_reverse ~80

Convert raw GPS latitude and longitude coordinates into structured street addresses, Plus Codes, neighborhoods, and Google Place IDs. Cost: 5 Credits / call.

NameTypeReqDescription
langstring–Optional ISO 639-1 language code.
latnumberyesLatitude (-90 to 90).
lngnumberyesLongitude (-180 to 180).

No output schema declared.

No examples provided.

leads_enrich ~102

Crawl a local business website domain in real time to extract public B2B email addresses, phone numbers, and LinkedIn, Instagram, Facebook, X/Twitter, YouTube, and TikTok profile URLs. Cost: 20 Credits when emails or social links are found (0 Credits if empty).

NameTypeReqDescription
domainstringyesBusiness domain or website URL, e.g. "austindentalspa.com" or "https://houndstoothcoffee.com".

No output schema declared.

No examples provided.

places_autocomplete ~107

Real-time typeahead place and street address predictions with optional coordinate and country biasing. Cost: 5 Credits / call (0 Credits if empty).

NameTypeReqDescription
langstring–Optional ISO 639-1 language code.
latnumber–Optional latitude bias.
lngnumber–Optional longitude bias.
qstringyesPartial place name or street address input.
regionstring–Optional ISO 3166-1 alpha-2 country code.

No output schema declared.

No examples provided.

places_details ~160

Retrieve the complete Google Business Profile by place_id, cid, or hex google_id including 1–5 star rating distribution, E.164 phone, website, categories, weekly work hours, and coordinates. Cost: 20 Credits / place (+20 if enrich_contacts=true and contacts found).

NameTypeReqDescription
enrich_contactsboolean–If true, also crawls the business website domain for B2B emails and social links.
langstring–ISO 639-1 language code.
place_idstringyesGoogle Maps Place ID (e.g. "ChIJ..."), numeric CID, or hex feature ID ("0x...:0x...").
regionstring–ISO 3166-1 alpha-2 country code.

No output schema declared.

No examples provided.

places_nearby ~143

Discover Google Maps businesses inside a geographic viewport around exact GPS coordinates (lat, lng, zoom). Cost: 5 Credits / place returned (0 Credits if empty).

NameTypeReqDescription
latnumberyesLatitude (-90 to 90), e.g. 30.2672.
limitinteger–Maximum places to return (1–100).
lngnumberyesLongitude (-180 to 180), e.g. -97.7431.
qstring–Optional category or keyword filter, e.g. "plumber" or "coffee".
zoomnumber–Map zoom level (3–21, default 14).

No output schema declared.

No examples provided.

places_photos ~80

Retrieve high-resolution storefront, interior, and menu photo URLs and dimensions for any Google Maps place. Cost: 2 Credits / photo returned (0 Credits if empty).

NameTypeReqDescription
limitinteger–Maximum photos to return (1–100).
place_idstringyesGoogle Maps Place ID ("ChIJ..."), CID, or hex feature ID.

No output schema declared.

No examples provided.

places_reviews ~152

Extract verified customer reviews for any Google Maps business sorted by newest, most_relevant, highest_rating, or lowest_rating, including reviewer profile, star rating, text, owner reply, and review photos. Cost: 2 Credits / review returned ($0.08–$0.20/1K reviews; 0 Credits if empty).

NameTypeReqDescription
langstring–ISO 639-1 language code.
limitinteger–Number of reviews to return (1–100).
offsetinteger–Pagination offset (>= 0).
place_idstringyesGoogle Maps Place ID ("ChIJ..."), CID, or hex feature ID.
sortstring–Review sort order.

No output schema declared.

No examples provided.

places_search ~242

Search Google Maps local businesses in real time by natural-language query (e.g. "HVAC contractors in Austin, TX") and return ratings, review counts, E.164 phone numbers, website domains, street addresses, opening hours, Place IDs, CIDs, and GPS coordinates. Cost: 5 Credits / place returned ($0.20–$0.50/1K places; 0 Credits if empty).

NameTypeReqDescription
enrich_contactsboolean–Set true to crawl returned business websites in real time for public B2B emails and social profiles.
langstring–ISO 639-1 language code (e.g. "en", "es", "de").
limitinteger–Maximum number of places to return (1–100).
offsetinteger–Pagination offset (>= 0).
qstringyesNatural-language search query, e.g. "Specialty coffee roasters in Austin, TX" or "Dental clinics in Miami, FL".
regionstring–ISO 3166-1 alpha-2 country/region bias (e.g. "us", "gb", "ca").

No output schema declared.

No examples provided.

Install

How do I install the Google Maps Places, Reviews & Local Leads API MCP Server server?

Google Maps Places, Reviews & Local Leads API MCP Server is a hosted endpoint at https://api.googlemapsapi.io/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.googlemapsapi.io

# add to Claude Code
claude mcp add --transport http io-googlemapsapi-mcp-server 'https://api.googlemapsapi.io/mcp'
Common questions

What is the Google Maps Places, Reviews & Local Leads API MCP Server server?

Google Maps Places, Reviews & Local Leads API MCP Server is listed in the public MCP registry as io.googlemapsapi/mcp-server. Real-time Google Maps local business leads, reviews, places & emails MCP. OAuth or API key. This page covers its hosted endpoint (https://api.googlemapsapi.io/mcp).

Is the Google Maps Places, Reviews & Local Leads API MCP Server server safe to use?

Google Maps Places, Reviews & Local Leads API MCP Server scores 23 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 Places, Reviews & Local Leads API MCP Server server expose?

Google Maps Places, Reviews & Local Leads API MCP Server exposes 8 tools: places_search, places_nearby, places_details, places_reviews, places_photos, and 3 more. Their descriptions and schemas cost roughly 1,066 tokens of context every time the server is loaded.

Does the Google Maps Places, Reviews & Local Leads API MCP Server server require authentication?

Its publisher declares no required credentials for Google Maps Places, Reviews & Local Leads API MCP Server. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Google Maps Places, Reviews & Local Leads API MCP Server server still maintained?

Google Maps Places, Reviews & Local Leads API MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 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 Maps Places, Reviews & Local Leads API MCP Server server?

VerifyMCP ran 5 checks on Google Maps Places, Reviews & Local Leads API MCP Server, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Google Maps Places, Reviews & Local Leads API MCP Server: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.