com.mcparmory/google-search vs io.github.DataLeadsPRO/google-serp
com.mcparmory/google-search is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.DataLeadsPRO/google-serp is an MCP server published by DataLeadsPRO. 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 |  com.mcparmory/google-search |  io.github.DataLeadsPRO/google-serp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (PyPI): 835 Downloads/week (PyPI): 162 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.0.2 Downloads/month (PyPI): 835 Downloads/week (PyPI): 162 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Not listed |
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 | com.mcparmory/google-search | io.github.DataLeadsPRO/google-serp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 32 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-google-search) | Remote server (data.dataleads.pro/mcp/google-serp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/dataleadspro/google-serp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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
com.mcparmory/google-search
Scrape Google search results with SERP data, ads, and knowledge panels
io.github.DataLeadsPRO/google-serp
Structured Google search, news, and local results at scale - organic results, news, and local packs
How to run each
com.mcparmory/google-search As a local MCP server: PyPI package
claude mcp add --transport stdio google-search -- uvx mcparmory-google-searchio.github.DataLeadsPRO/google-serp As a remote MCP server
claude mcp add --transport http google-serp https://data.dataleads.pro/mcp/google-serpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/google-serp 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: com.mcparmory/google-search · What it can do: io.github.DataLeadsPRO/google-serp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.