Ext Ops Panel
Open dashboard
Comparison

public-apis-live vs Cite42

public-apis-live is a plugin bundle for AI coding tools published by Manavarya09. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Cite42 is an MCP server published by cite42.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
Marketplacepublic-apis-liveCite42
Community marketplace manavarya09/public-apis-live Listed
Version: 0.2.0
Forks (GitHub): 14
Stars (GitHub): 156
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.3
Downloads/month (npm): 1 687
Downloads/week (npm): 448
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.8.3
Downloads/month (npm): 1 687
Downloads/week (npm): 448
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

public-apis-live vs Cite42
Factpublic-apis-liveCite42
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)156 (better)0 (worse)
Forks (GitHub) (differs)14 (better)0 (worse)
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (public-apis-live-mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/manavarya09/public-apis-livegithub.com/cite42/mcp
Changes in the last 7 days22
First seen (differs)2026-10-272026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago, requires a key

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

public-apis-live

In its own words, on Community GitHub marketplaces:

Discover working public APIs for any task — auto-verified for reachability and refreshed daily. Adds search_apis / get_api / list_categories tools and a skill that tells the agent to pick a working API.

Cite42

In its own words, on Official MCP Registry:

AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers.

How to run each

public-apis-live As a Claude Code plugin

Claude Code
/plugin marketplace add manavarya09/public-apis-live
/plugin install public-apis-live@public-apis-live

Cite42 As a remote MCP server

Claude Code
claude mcp add --transport http cite42 https://mcp.cite42.dev

Requires: CITE42_API_KEY (secret)

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

Only Cite42 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 public-apis-live publish no settings it asks for, so we do not compare settings.

What it can do: public-apis-live · What it can do: Cite42 · 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. Package data comes from the public npm registry (registry.npmjs.org). 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