Ext Ops Panel
Open dashboard
Comparison

Search1API vs Web Search

Search1API is a plugin bundle for AI coding tools published by Search1API. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Web Search is an MCP server published by hec-ovi. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplaceSearch1APIWeb Search
Community marketplace superagents-lab/search1api-mcp Listed
Version: 1.2.1
Forks (GitHub): 38
Stars (GitHub): 173
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.6
Downloads/month (PyPI): 258
Downloads/week (PyPI): 50
Forks (GitHub): 1
Stars (GitHub): 8
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

Search1API vs Web Search
FactSearch1APIWeb Search
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)173 (better)8 (worse)
Forks (GitHub) (differs)38 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.search1api.com/mcp)On your machine (websearch-skill)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle22
LicenceMITMIT
Repository (differs)github.com/superagents-lab/search1api-mcpgithub.com/hec-ovi/websearch-skill
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno remote endpoint we check

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

Search1API

In its own words, on Community GitHub marketplaces:

Search1API brings multi-engine search to AI agents, with Google, Bing, DuckDuckGo, Yahoo, and specialized sources including GitHub, Reddit, X, arXiv, Wikipedia, YouTube, WeChat, and Bilibili. Choose sources that fit your task and compare findings across them. Read full pages, search current news, discover site links, and explore GitHub and Hacker News trends. Browse selected results in interactive source cards, with expandable source lists and links to the original pages. Results include source URLs for citation.

Web Search

In its own words, on Official MCP Registry:

Keyless multi-engine web search, fetch, and clean-Markdown read for AI agents. No API keys.

How to run each

Search1API As a Codex plugin

Codex
codex plugin marketplace add superagents-lab/search1api-mcp

Web Search As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio web-search -- uvx websearch-skill mcp

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

Only Search1API 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

Neither one's marketplaces publish the settings it asks for.

What it can do: Search1API · What it can do: Web Search · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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