CrawlerData: Google Shopping & SERP vs io.github.DataLeadsPRO/google-serp
CrawlerData: Google Shopping & SERP is an MCP server published by crawlerdata.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-24. 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 |  CrawlerData: Google Shopping & SERP |  io.github.DataLeadsPRO/google-serp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.1 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 | CrawlerData: Google Shopping & SERP | io.github.DataLeadsPRO/google-serp |
|---|---|---|
| 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 (api.crawlerdata.com/mcp) | Remote server (data.dataleads.pro/mcp/google-serp) |
| 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) | Not stated | github.com/dataleadspro/google-serp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 6 h ago | Responded 12 h 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
CrawlerData: Google Shopping & SERP
Google Shopping products and seller prices, plus Google Search, Images, News and Local results.
io.github.DataLeadsPRO/google-serp
Structured Google search, news, and local results at scale - organic results, news, and local packs
How to run each
CrawlerData: Google Shopping & SERP As a remote MCP server
claude mcp add --transport http google-shopping-serp https://api.crawlerdata.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
io.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.
Both endpoints responded at the last daily 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: CrawlerData: Google Shopping & SERP · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.