public-apis-live vs Upstream
public-apis-live is a plugin bundle for AI coding tools published by Manavarya09. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Upstream is an MCP server published by toolweather. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace | ||
|---|---|---|
| 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.2.0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) 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
| Fact | public-apis-live | Upstream |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 156 | 0 (last published figure) |
| Forks (GitHub) (differs) | 14 | 0 (last published figure) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (public-apis-live-mcp) | Remote server (upstream.toolweather.workers.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/manavarya09/public-apis-live | github.com/toolweather/upstream |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-27 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 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
public-apis-live
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.
Upstream
Is this AI/dev API down? Is this model deprecated, what replaces it? Live status for ~40 APIs.
How to run each
public-apis-live As a Claude Code plugin
/plugin marketplace add manavarya09/public-apis-live
/plugin install public-apis-live@public-apis-live
Upstream As a remote MCP server
claude mcp add --transport http upstream https://upstream.toolweather.workers.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"
Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Upstream 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: public-apis-live · What it can do: Upstream · 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.