com.thenextgennexus/google-maps-mcp-server
REMOTE · NEXGENDATA-MCP-PROXY.STEVE-CORBEIL.WORKERS.DEV
Local business lead extraction with email + phone enrichment from Google Maps.
Available components
Last scanned (17 minutes ago)
Scores higher than 13% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security46
- 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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → 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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/google-maps-mcp-server/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=steve-corbeil.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6e32f0f7b6603192ea15291f88ce9af0302 |
| SANs: *.steve-corbeil.workers.dev, steve-corbeil.workers.dev | ||||||
| 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 nexgendata-mcp-proxy.steve-corbeil.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://nexgendata-mcp-proxy.steve-corbeil.workers.dev/google-maps-mcp-server/mcp | Verified | 200 | |
| http (plaintext) | http://nexgendata-mcp-proxy.steve-corbeil.workers.dev/google-maps-mcp-server/mcp | Inconclusive | 405 |
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 →
generate_leads ~170
Extract B2B lead lists from Google Maps by business category and geography. Returns company name, full address, contact phone, website, business category, and review metrics. Use for sales prospecting, market research, or building vendor lists. Returns 20+ leads per query by default.
| Name | Type | Req | Description |
|---|---|---|---|
| business_type | string | yes | Industry or business category to target (e.g. 'HVAC contractors', 'dental clinics', 'software development firms') |
| city | string | yes | City where businesses are located (e.g. 'Denver', 'New York', 'San Francisco') |
| max_results | integer | – | Number of leads to generate (default 20, recommended for data quality) |
| state | string | – | State or region abbreviation (e.g. 'CO', 'NY', 'CA') |
No output schema declared.
No examples provided.
search_local_businesses ~156
Search Google Maps for local businesses matching a query and location. Returns business name, complete address, star rating, review count, phone number, website URL, and business category. Use for restaurant discovery, service provider lookup, or competitive local analysis. Returns open/closed status.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Geographic location as city, zip code, or address (e.g. 'Los Angeles, CA', '90210', '1600 Pennsylvania Ave') |
| max_results | integer | – | Number of business results to return (default 10, max 50 for large searches) |
| query | string | yes | Business type or name to find (e.g. 'plumbers near me', 'Thai restaurants', 'Starbucks') |
No output schema declared.
No examples provided.
validate_emails ~79
Validate and verify email addresses for deliverability, format compliance, and mailbox existence. Returns pass/fail status per email, syntax errors, domain validity, and SMTP verification result. Use before sending bulk emails to prevent bounces and protect sender reputation.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Array of email addresses to validate for syntax, domain, and deliverability |
No output schema declared.
No examples provided.
How do I install the com.thenextgennexus/google-maps-mcp-server server?
com.thenextgennexus/google-maps-mcp-server is a hosted endpoint at https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/google-maps-mcp-server/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 · nexgendata-mcp-proxy.steve-corbeil.workers.dev
claude mcp add --transport http com-thenextgennexus-google-maps-mcp-server 'https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/google-maps-mcp-server/mcp'
What is the com.thenextgennexus/google-maps-mcp-server server?
com.thenextgennexus/google-maps-mcp-server is listed in the public MCP registry as com.thenextgennexus/google-maps-mcp-server. Local business lead extraction with email + phone enrichment from Google Maps. This page covers its hosted endpoint (https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/google-maps-mcp-server/mcp).
Is the com.thenextgennexus/google-maps-mcp-server server safe to use?
com.thenextgennexus/google-maps-mcp-server scores 28 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.thenextgennexus/google-maps-mcp-server server expose?
com.thenextgennexus/google-maps-mcp-server exposes 3 tools: search_local_businesses, generate_leads, validate_emails. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.
Does the com.thenextgennexus/google-maps-mcp-server server require authentication?
No. We connected to com.thenextgennexus/google-maps-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.thenextgennexus/google-maps-mcp-server server still maintained?
com.thenextgennexus/google-maps-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.