com.placesdataapi/google-maps-places-mcp
REMOTE · API.PLACESDATAAPI.COM · 2 COMPONENTS
Local business places search, reviews, ratings, geocoding & contact enrichment API for agents.
Available components
Last scanned (21 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 1275 tokens (~141/item across 9 items; 9 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 Management3
- Stability observed for 1 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 21 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Nov 26 72
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 21 Nov 2026 · Probed https://api.placesdataapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=placesdataapi.com | CN=YE1,O=Let's Encrypt,C=US | 7 Nov 2026 | 5 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6d26dbdd016db3c36c98c6b131992019cb3 |
| SANs: *.placesdataapi.com, placesdataapi.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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.placesdataapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| placesdataapi.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.placesdataapi.com/.well-known/oauth-protected-resource", scope="mcp:tools:read"
Bearer resource_metadata="https://api.placesdataapi.com/.well-known/oauth-protected-resource", scope="mcp:tools:read" Protected resource metadata
| Document | https://api.placesdataapi.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.placesdataapi.com/mcp |
| Authorisation server | https://api.placesdataapi.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.placesdataapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.placesdataapi.com/mcp | HTTPS enforced | 301 | https://api.placesdataapi.com/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 →
geocode_reverse Reverse Geocode GPS Coordinates to Address & Place ID ~80
Convert raw GPS latitude and longitude coordinates into structured street addresses, Plus Codes, neighborhoods, and Google Place IDs. Cost: 5 Credits / call.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Optional ISO 639-1 language code. |
| lat | number | yes | Latitude (-90 to 90). |
| lng | number | yes | Longitude (-180 to 180). |
No output schema declared.
No examples provided.
leads_enrich Enrich Business Website Domain with B2B Emails & Social Links ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Business domain or website URL, e.g. "austindentalspa.com" or "https://houndstoothcoffee.com". |
No output schema declared.
No examples provided.
places_autocomplete Google Maps Place & Address Autocomplete ~107
Real-time typeahead place and street address predictions with optional coordinate and country biasing. Cost: 5 Credits / call (0 Credits if empty).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Optional ISO 639-1 language code. |
| lat | number | – | Optional latitude bias. |
| lng | number | – | Optional longitude bias. |
| q | string | yes | Partial place name or street address input. |
| region | string | – | Optional ISO 3166-1 alpha-2 country code. |
No output schema declared.
No examples provided.
places_details Get Full Google Business Profile 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).
| Name | Type | Req | Description |
|---|---|---|---|
| enrich_contacts | boolean | – | If true, also crawls the business website domain for B2B emails and social links. |
| lang | string | – | ISO 639-1 language code. |
| place_id | string | yes | Google Maps Place ID (e.g. "ChIJ..."), numeric CID, or hex feature ID ("0x...:0x..."). |
| region | string | – | ISO 3166-1 alpha-2 country code. |
No output schema declared.
No examples provided.
places_nearby Discover Nearby Businesses by GPS Coordinates ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (-90 to 90), e.g. 30.2672. |
| limit | integer | – | Maximum places to return (1–100). |
| lng | number | yes | Longitude (-180 to 180), e.g. -97.7431. |
| q | string | – | Optional category or keyword filter, e.g. "plumber" or "coffee". |
| zoom | number | – | Map zoom level (3–21, default 14). |
No output schema declared.
No examples provided.
places_photos Fetch Business Storefront, Interior & Menu 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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum photos to return (1–100). |
| place_id | string | yes | Google Maps Place ID ("ChIJ..."), CID, or hex feature ID. |
No output schema declared.
No examples provided.
places_reviews Extract Verified Google Maps Customer 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).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | ISO 639-1 language code. |
| limit | integer | – | Number of reviews to return (1–100). |
| offset | integer | – | Pagination offset (>= 0). |
| place_id | string | yes | Google Maps Place ID ("ChIJ..."), CID, or hex feature ID. |
| sort | string | – | Review sort order. |
No output schema declared.
No examples provided.
places_search Search Google Maps Local Businesses ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| enrich_contacts | boolean | – | Set true to crawl returned business websites in real time for public B2B emails and social profiles. |
| lang | string | – | ISO 639-1 language code (e.g. "en", "es", "de"). |
| limit | integer | – | Maximum number of places to return (1–100). |
| offset | integer | – | Pagination offset (>= 0). |
| q | string | yes | Natural-language search query, e.g. "Specialty coffee roasters in Austin, TX" or "Dental clinics in Miami, FL". |
| region | string | – | ISO 3166-1 alpha-2 country/region bias (e.g. "us", "gb", "ca"). |
No output schema declared.
No examples provided.
whatsapp_check Verify WhatsApp Registration, Business Account & ITU Numbering Plan ~125
Validate whether an E.164 phone number is registered on WhatsApp, detect WhatsApp Business accounts, resolve its WhatsApp JID (<digits>@s.whatsapp.net), and return ITU international country/numbering plan metadata. Cost: 3 Credits / valid check ($0.12–$0.30 per 1K checks; 0 Credits on invalid synthetic numbers or errors).
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | International E.164 phone number (e.g. "+18002428478" or "+447911123456"). Spaces and hyphens are stripped automatically. |
No output schema declared.
No examples provided.
How do I install the com.placesdataapi/google-maps-places-mcp server?
com.placesdataapi/google-maps-places-mcp is a hosted endpoint at https://api.placesdataapi.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.placesdataapi.com
claude mcp add --transport http com-placesdataapi-google-maps-places-mcp 'https://api.placesdataapi.com/mcp'
What is the com.placesdataapi/google-maps-places-mcp server?
com.placesdataapi/google-maps-places-mcp is listed in the public MCP registry as com.placesdataapi/google-maps-places-mcp. Local business places search, reviews, ratings, geocoding & contact enrichment API for agents. This page covers its hosted endpoint (https://api.placesdataapi.com/mcp).
Is the com.placesdataapi/google-maps-places-mcp server safe to use?
com.placesdataapi/google-maps-places-mcp scores 73 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 com.placesdataapi/google-maps-places-mcp server expose?
com.placesdataapi/google-maps-places-mcp exposes 9 tools: places_search, places_nearby, places_details, places_reviews, places_photos, and 4 more. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.
Does the com.placesdataapi/google-maps-places-mcp server require authentication?
Yes. com.placesdataapi/google-maps-places-mcp 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 com.placesdataapi/google-maps-places-mcp server still maintained?
com.placesdataapi/google-maps-places-mcp 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 com.placesdataapi/google-maps-places-mcp server?
VerifyMCP ran 13 checks on com.placesdataapi/google-maps-places-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.