Ext Ops Panel
Open dashboard
Comparison

serpapi-claude-plugin vs com.pulsemcp/serpapi-hotels

serpapi-claude-plugin is a plugin bundle for AI coding tools published by serpapi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.pulsemcp/serpapi-hotels is an MCP server published by pulsemcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplaceserpapi-claude-plugincom.pulsemcp/serpapi-hotels
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 17
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.0.4
Downloads/month (npm): 175
Downloads/week (npm): 31
Forks (GitHub): 10
Stars (GitHub): 81
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

serpapi-claude-plugin vs com.pulsemcp/serpapi-hotels
Factserpapi-claude-plugincom.pulsemcp/serpapi-hotels
Marketplaces that list it11
Stars (GitHub) (differs)17 (worse)81 (better)
Forks (GitHub) (differs)2 (worse)10 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (serpapi-hotels-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/serpapi/serpapi-claude-plugingithub.com/pulsemcp/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

serpapi-claude-plugin

In its own words, on Claude Code: claude-plugins-community:

A Claude Code plugin that gives Claude the ability to search Google, Amazon, Walmart, YouTube, Google Maps, Google Scholar, and 100+ other engines via the SerpApi REST API.

com.pulsemcp/serpapi-hotels

In its own words, on Official MCP Registry:

MCP server for searching Google Hotels via SerpAPI — hotel search, pricing, ratings, and reviews.

How to run each

serpapi-claude-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install serpapi-claude-plugin@claude-community

com.pulsemcp/serpapi-hotels As a local MCP server: npm package

Claude Code
claude mcp add --env "SERPAPI_API_KEY=<YOUR_SERPAPI_API_KEY>" --transport stdio serpapi-hotels -- npx -y serpapi-hotels-mcp-server

Requires: SERPAPI_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

The marketplaces of serpapi-claude-plugin publish no settings it asks for, so we do not compare settings.

What it can do: serpapi-claude-plugin · What it can do: com.pulsemcp/serpapi-hotels · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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