Ext Ops Panel
Open dashboard
Comparison

LinkedIn Ads Library (unofficial) vs ProspectAPIs

LinkedIn Ads Library (unofficial) is an MCP server published by adpeekly.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-11. 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
MarketplaceLinkedIn Ads Library (unofficial)ProspectAPIs
Official MCP Registry Listed
Version: 1.0.1
No figure published
Not marked · First seen
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

LinkedIn Ads Library (unofficial) vs ProspectAPIs
FactLinkedIn Ads Library (unofficial)ProspectAPIs
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 (spkftjsjduykrvzeuzld.supabase.co/functions/v1/mcp-server)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
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/prospectapis/prospectapis-mcp
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Status out of date: last check 40 h ago returned HTTP 405Status out of date: last check 43 h ago returned HTTP 405

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

LinkedIn Ads Library (unofficial)

In its own words, on Official MCP Registry:

Unofficial read-only search over LinkedIn's public Ad Library: 253,610 B2B ads with durations.

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

LinkedIn Ads Library (unofficial) As a remote MCP server

Claude Code
claude mcp add --transport http linkedin-ads-library https://spkftjsjduykrvzeuzld.supabase.co/functions/v1/mcp-server --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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 LinkedIn Ads Library (unofficial) publish no settings it asks for, so we do not compare settings.

What it can do: LinkedIn Ads Library (unofficial) · What it can do: ProspectAPIs · Compare two other plugins

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