Ext Ops Panel
Open dashboard
Comparison

Buscador: Google vs SerpApi

Buscador: Google is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). SerpApi is an MCP server published by serpapi. 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

Where each is published
MarketplaceBuscador: GoogleSerpApi
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.0.0
Forks (GitHub): 44
Stars (GitHub): 182
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

Buscador: Google vs SerpApi
FactBuscador: GoogleSerpApi
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)182 (better)
Forks (GitHub) (differs)0 (worse)44 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.mcp.ai/p_buscador_google)Remote server (mcp.serpapi.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/mcp-dir/buscador_google-mcpgithub.com/serpapi/serpapi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agoResponded 6 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

Buscador: Google

In its own words, on Official MCP Registry:

Buscador: Google, official-source lookup. Platform-hosted, pay per query with prepaid credit.

SerpApi

In its own words, on Official MCP Registry:

Official SerpApi MCP server for Google, Bing, and other search engines.

How to run each

Buscador: Google As a remote MCP server

Claude Code
claude mcp add --transport http buscador-google-mcp https://api.mcp.ai/p_buscador_google

SerpApi As a remote MCP server

Claude Code
claude mcp add --transport http serpapi-mcp https://mcp.serpapi.com/mcp --header "Authorization: Bearer <YOUR_SERPAPI_API_KEY>"

Requires: Authorization header

Commands 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: Buscador: Google · What it can do: SerpApi · 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.

Where the data comes from: how the catalog is built