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.

PlacesDataAPI — Google Maps Places, Reviews & Geocoding MCP. Zero-signup x40

REMOTE · API.PLACESDATAAPI.COM · 2 COMPONENTS

Google Maps Places, Reviews & Geocoding MCP. Zero-signup x402 USDC ($0.0015) on Base or API key.

73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security89
Transport & Reachability100
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 Management7
  • Stability observed for 2 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
What we tested

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 →

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.

  • 20 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 19 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.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
MCP tools · 9 exposed · ~1,191 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.

whatsapp_check ~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).

NameTypeReqDescription
phonestringyesInternational E.164 phone number (e.g. "+18002428478" or "+447911123456"). Spaces and hyphens are stripped automatically.

No output schema declared.

No examples provided.

Install

How do I install the PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server?

PlacesDataAPI — Google Maps Places, Reviews & Geocoding… 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

# add to Claude Code
claude mcp add --transport http com-placesdataapi-x402-google-maps-places-review 'https://api.placesdataapi.com/mcp'
Common questions

What is the PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server?

PlacesDataAPI — Google Maps Places, Reviews & Geocoding… is an MCP server listed in the public MCP registry as com.placesdataapi/x402-google-maps-places-reviews-mcp. Google Maps Places, Reviews & Geocoding MCP. Zero-signup x402 USDC ($0.0015) on Base or API key. This page covers its hosted endpoint (https://api.placesdataapi.com/mcp).

Is the PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server safe to use?

PlacesDataAPI — Google Maps Places, Reviews & Geocoding… 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 PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server expose?

PlacesDataAPI — Google Maps Places, Reviews & Geocoding… 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 PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server require authentication?

Yes. PlacesDataAPI — Google Maps Places, Reviews & Geocoding… 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 PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server still maintained?

PlacesDataAPI — Google Maps Places, Reviews & Geocoding… 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 PlacesDataAPI — Google Maps Places, Reviews & Geocoding… MCP server?

VerifyMCP ran 13 checks on PlacesDataAPI — Google Maps Places, Reviews & Geocoding…, 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.