Ext Ops Panel
Open dashboard
Comparison

com.jojapi/googlesearch-api vs Olostep MCP Server

com.jojapi/googlesearch-api is an MCP server published by jojapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). Olostep MCP Server is an MCP server published by olostep. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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

Where each is published
Marketplacecom.jojapi/googlesearch-apiOlostep MCP Server
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.18
Downloads/month (npm): 763
Downloads/week (npm): 220
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
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

com.jojapi/googlesearch-api vs Olostep MCP Server
Factcom.jojapi/googlesearch-apiOlostep MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-25
Where it runs (differs)Remote server (mcp.jojapi.com/googlesearch-api)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)Not a bundle14
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/olostep/olostep-claude-code-plugin
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agonot checked yet

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.jojapi/googlesearch-api

In its own words, on Official MCP Registry:

GoogleSearch API: Fetch real-time Google Search results including title, links Ideal for serp api.

Olostep MCP Server

In its own words, on Official MCP Registry:

Search, scrape, and crawl the web for AI agents. Batch scraping and answers with citations.

How to run each

com.jojapi/googlesearch-api As a remote MCP server

Claude Code
claude mcp add --transport http googlesearch-api https://mcp.jojapi.com/googlesearch-api

Olostep MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http olostep-mcp-server https://mcp.olostep.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only com.jojapi/googlesearch-api 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

The marketplaces of com.jojapi/googlesearch-api publish no settings it asks for, so we do not compare settings.

What it can do: com.jojapi/googlesearch-api · What it can do: Olostep MCP Server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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