SEO Tools: A-Parser bridge vs Google Search — FlashData
SEO Tools: A-Parser bridge is an MCP server published by antohins. Marketplaces we read that list it: 1 (Official MCP Registry). Google Search — FlashData is an MCP server published by flashdata-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  SEO Tools: A-Parser bridge |  Google Search — FlashData |
|---|---|---|
| Official MCP Registry | Listed Version: 1.8.0 Downloads/month (npm): 215 Downloads/week (npm): 52 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Listed Version: 0.1.2 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 | SEO Tools: A-Parser bridge | Google Search — FlashData |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (seo-tools-mcp-aparser) | On your machine (https://github.com/rocosen/flashdata-mcp/releases/download/smithery-task-servers-v0.1.1/flashdata-google-search-0.1.1.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/antohins/seo-tools-mcp | github.com/rocosen/flashdata-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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
SEO Tools: A-Parser bridge
Bridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only).
Google Search — FlashData
Google Search rankings, URLs and snippets for localized SERP research. Paid FlashData API.
How to run each
SEO Tools: A-Parser bridge As a local MCP server: npm package
claude mcp add --env "APARSER_PASSWORD=<YOUR_APARSER_PASSWORD>" --transport stdio seo-tools-mcp-aparser -- npx -y seo-tools-mcp-aparserRequires: APARSER_PASSWORD (secret)
Google Search — FlashData
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: FLASHDATA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only SEO Tools: A-Parser bridge asks for
APARSER_GOOGLE_PRESETAPARSER_PASSWORD (secret)APARSER_PROXY_CHECKERSAPARSER_URLAPARSER_USE_PROXYAPARSER_YANDEX_PRESET
Only Google Search — FlashData asks for
FLASHDATA_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: SEO Tools: A-Parser bridge · What it can do: Google Search — FlashData · 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.