io.github.JienWeng/x402-osint vs OpenOSINT
io.github.JienWeng/x402-osint is an MCP server published by JienWeng. Marketplaces we read that list it: 1 (Official MCP Registry). OpenOSINT is an MCP server published by OpenOSINT. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
| Marketplace |  OpenOSINT | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 2.36.0 Downloads/month (PyPI): 2 744 Downloads/week (PyPI): 1 295 Forks (GitHub): 280 Stars (GitHub): 1 771 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
| Fact | io.github.JienWeng/x402-osint | OpenOSINT |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 771 |
| Forks (GitHub) (differs) | No figure on GitHub | 280 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (x402-osint.tail66f665.ts.net/sse) | On your machine (openosint) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 5 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/openosint/openosint |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
io.github.JienWeng/x402-osint
Pay-per-call OSINT for AI agents: username + email recon in USDC on Base via x402.
OpenOSINT
AI-powered OSINT agent & MCP server. 21 tools: email, breach, IP, WHOIS, DNS, Shodan, GitHub & more.
How to run each
io.github.JienWeng/x402-osint As a remote MCP server
claude mcp add --transport sse x402-osint https://x402-osint.tail66f665.ts.net:8443/sseOpenOSINT As a local MCP server: PyPI package
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 openosintRequires: ABUSEIPDB_API_KEY (secret), ANTHROPIC_API_KEY (secret), HIBP_API_KEY (secret), IP2LOCATION_API_KEY (secret), IPINFO_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.JienWeng/x402-osint 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
The marketplaces of io.github.JienWeng/x402-osint publish no settings it asks for, so we do not compare settings.
What it can do: io.github.JienWeng/x402-osint · What it can do: OpenOSINT · 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.