Ext Ops Panel
Open dashboard
Comparison

linkedin-scam-detector vs OSINT.SX

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). OSINT.SX is an MCP server published by osintsx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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-detectorOSINT.SX
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: 0.1.3
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-scam-detector vs OSINT.SX
Factlinkedin-scam-detectorOSINT.SX
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (osintsx-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/oopsyz/linkedin-scam-detectorgithub.com/osintsx/osintsx-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-30

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.

OSINT.SX

In its own words, on Official MCP Registry:

Search an email, phone, username or name across every OSINT.SX source, plus account history tools.

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

OSINT.SX As a local MCP server: npm package

Claude Code
claude mcp add --env "OSINTSX_API_KEY=<YOUR_OSINTSX_API_KEY>" --transport stdio osintsx-mcp -- npx -y osintsx-mcp

Requires: OSINTSX_API_KEY (secret)

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

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-scam-detector publish no settings it asks for, so we do not compare settings.

What it can do: linkedin-scam-detector · What it can do: OSINT.SX · 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