Ext Ops Panel
Open dashboard
Comparison

UnifAPI vs ProspectAPIs

UnifAPI is a plugin bundle for AI coding tools published by UnifAPI. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ProspectAPIs is an MCP server published by ProspectAPIs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
MarketplaceUnifAPIProspectAPIs
Community marketplace unifapi-agent/agents Listed
Version: 1.0.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 0.2.5
Downloads/month (npm): 3 268
Downloads/week (npm): 2 219
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.17.1
Downloads/month (npm): 3 268
Downloads/week (npm): 2 219
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

UnifAPI vs ProspectAPIs
FactUnifAPIProspectAPIs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-07
Where it runs (differs)Remote server (mcp.unifapi.com)Remote server or your machine
Transport (differs)Streamable HTTPstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)48Not a bundle
LicenceMITMIT
Repository (differs)github.com/unifapi-agent/agentsgithub.com/prospectapis/prospectapis-mcp
Changes in the last 7 days (differs)210
First seen (differs)2026-11-092026-10-12
Endpoint at the last check (differs)Status out of date: last check 44 h ago returned HTTP 405Responded 12 h 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

UnifAPI

In its own words, on Community GitHub marketplaces:

Marketing-agent skills + the UnifAPI public-data MCP server (OAuth, read-only). One install for skills and live data together.

ProspectAPIs

In its own words, on Official MCP Registry:

Moved to com.prospectapis/prospectapis-mcp. Install prospectapis-mcp from npm for the latest.

How to run each

UnifAPI As a Claude Code plugin

Claude Code
/plugin marketplace add unifapi-agent/agents
/plugin install unifapi@unifapi

ProspectAPIs As a local MCP server: npm package

Claude Code
claude mcp add --env "PROSPECTAPIS_API_KEY=<YOUR_PROSPECTAPIS_API_KEY>" --transport stdio prospectapis-mcp -- npx -y prospectapis-mcp

Requires: PROSPECTAPIS_API_KEY (secret)

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

Both endpoints responded at the last daily 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 UnifAPI publish no settings it asks for, so we do not compare settings.

What it can do: UnifAPI · What it can do: ProspectAPIs · 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