Ext Ops Panel
Open dashboard
Comparison

OpenOSINT vs OSINT.SX

OpenOSINT is an MCP server published by OpenOSINT. Marketplaces we read that list it: 1 (Official MCP Registry). 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-07. 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
MarketplaceOpenOSINTOSINT.SX
Official MCP Registry Listed
Version: 2.38.0
Downloads/month (PyPI): 2 744
Downloads/week (PyPI): 1 471
Forks (GitHub): 291
Stars (GitHub): 1 863
Not marked · First seen
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

OpenOSINT vs OSINT.SX
FactOpenOSINTOSINT.SX
Marketplaces that list it11
Stars (GitHub) (differs)1 863 (better)0 (worse)
Forks (GitHub) (differs)291 (better)0 (worse)
Last release (differs)2026-11-05Not published
Where it runs (differs)On your machine (openosint)On your machine (osintsx-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 51, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/openosint/openosintgithub.com/osintsx/osintsx-mcp
Changes in the last 7 days (differs)30
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

OpenOSINT

In its own words, on Official MCP Registry:

AI-powered OSINT agent & MCP server. 21 tools: email, breach, IP, WHOIS, DNS, Shodan, GitHub & more.

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

OpenOSINT As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ABUSEIPDB_API_KEY=<YOUR_ABUSEIPDB_API_KEY>" --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "HIBP_API_KEY=<YOUR_HIBP_API_KEY>" --env "IP2LOCATION_API_KEY=<YOUR_IP2LOCATION_API_KEY>" --env "IPINFO_TOKEN=<YOUR_IPINFO_TOKEN>" --transport stdio openosint -- uvx openosint

Requires: ABUSEIPDB_API_KEY (secret), ANTHROPIC_API_KEY (secret), HIBP_API_KEY (secret), IP2LOCATION_API_KEY (secret), IPINFO_TOKEN (secret)

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

Only OpenOSINT asks for

  • ABUSEIPDB_API_KEY (secret)
  • ANTHROPIC_API_KEY (secret)
  • HIBP_API_KEY (secret)
  • IP2LOCATION_API_KEY (secret)
  • IPINFO_TOKEN (secret)

Only OSINT.SX asks for

  • OSINTSX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: OpenOSINT · What it can do: OSINT.SX · Compare two other plugins

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