io.github.DataLeadsPRO/google-maps-leads vs LocationLists
io.github.DataLeadsPRO/google-maps-leads is an MCP server published by DataLeadsPRO. Marketplaces we read that list it: 1 (Official MCP Registry). LocationLists is an MCP server published by kylehawke-stack. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.DataLeadsPRO/google-maps-leads |  LocationLists |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.DataLeadsPRO/google-maps-leads | LocationLists |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (data.dataleads.pro/mcp/google-maps-leads) | Remote server (locationlists.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dataleadspro/google-maps-leads | github.com/kylehawke-stack/locationlists-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.DataLeadsPRO/google-maps-leads
Turn Maps queries into lead lists: businesses, phones, websites, and reviews with async job control.
LocationLists
US business location data: search, sample, count, query rows or buy CSVs (Stripe or x402 USDC).
How to run each
io.github.DataLeadsPRO/google-maps-leads As a remote MCP server
claude mcp add --transport http google-maps-leads https://data.dataleads.pro/mcp/google-maps-leadsLocationLists As a remote MCP server
claude mcp add --transport http locationlists https://locationlists.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/google-maps-leads has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.DataLeadsPRO/google-maps-leads · What it can do: LocationLists · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.