Ext Ops Panel
Open dashboard
Comparison

linkedin-scam-detector vs EnvoAPI

linkedin-scam-detector is a plugin bundle for AI coding tools published by oopsyz. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). EnvoAPI is an MCP server published by envoapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplacelinkedin-scam-detectorEnvoAPI
Claude Code: claude-plugins-community Listed
Version: 6a69d05
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.2
No figure published
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-scam-detector vs EnvoAPI
Factlinkedin-scam-detectorEnvoAPI
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.envoapi.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/oopsyz/linkedin-scam-detectorNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

linkedin-scam-detector

In its own words, on Claude Code: claude-plugins-community:

Detect fake recruiter emails and job offer scams. Requires Claude Code and the Claude in Chrome extension. Opens your email in the browser, analyzes the message, verifies the sender domain and email format against company directories, checks the recruiter's LinkedIn profile directly, searches for the job posting on the company's careers page, and finds a verified phone number to call back — with warnings about spoofed caller ID.

EnvoAPI

In its own words, on Official MCP Registry:

People, company, job and LinkedIn post data, plus email finding and verification.

How to run each

linkedin-scam-detector As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install linkedin-scam-detector@claude-community

EnvoAPI As a remote MCP server

Claude Code
claude mcp add --transport http envoapi https://api.envoapi.com/mcp

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

Only EnvoAPI 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: linkedin-scam-detector · What it can do: EnvoAPI · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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