Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS vs io.github.TheNextGenNexus/google-maps-mcp-server
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS is an MCP server published by cybermax.cybermax-tools.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.TheNextGenNexus/google-maps-mcp-server is an MCP server published by TheNextGenNexus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS |  io.github.TheNextGenNexus/google-maps-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 98 Downloads/week (npm): 10 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 | Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS | io.github.TheNextGenNexus/google-maps-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (pinloft.cybermaxtools.com/mcp) | On your machine (@thenextgennexus/google-maps-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/thenextgennexus/business-data-mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
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
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS
Pinloft: US address to lat/lon, county, FIPS; reverse geocoding. Free, no key.
io.github.TheNextGenNexus/google-maps-mcp-server
Search local businesses, generate leads, and validate emails via Google Maps data
How to run each
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: x-api-key header
io.github.TheNextGenNexus/google-maps-mcp-server As a local MCP server: npm package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio google-maps-mcp-server -- npx -y @thenextgennexus/google-maps-mcp-serverRequires: APIFY_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS 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
The marketplaces of Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS publish no settings it asks for, so we do not compare settings.
What it can do: Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS · What it can do: io.github.TheNextGenNexus/google-maps-mcp-server · 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.