Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

OSINT

by robyroroversion 0.3.0i★ –iRuns on your computer
Registry nameio.github.robyroro/osint-mcp

Install

Overview

Description from the maker (original English)

Domain and website investigations: batch recon, shared infrastructure, CT history and public lookups

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "osint": {
      "command": "uvx",
      "args": [
        "osint-mcp-server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add osint -- uvx osint-mcp-server

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "osint": {
      "command": "uvx",
      "args": [
        "osint-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "osint": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "osint-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account robyroro, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Cybersecurityi

  • More stars than 0% of the other 995 servers in this category
  • Published to the registry more recently than 57% of the other 995 servers in this category
  • Basic checks equal to or better than 100% of the other 995 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is OSINT safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 33 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: WatchGuard MCP, ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

WatchGuard MCP

by servosity

WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer

Runs on your computerUpdated today
Install

Look up location, network, company and threat data for IP addresses and ASNs in ipdata.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

osint-mcp

MCP tools for investigating domains, IPs and websites. Look up public records, compare infrastructure, check several domains at once, or collect the details behind a suspicious site. No API keys needed.

I got tired of jumping between whois, crt.sh, the Wayback Machine and Shodan tabs when looking into a domain, so this lets the model do it and put the results together.

Tools

toolwhat it doessource
recon_domaindomain overview, highlights and coverage for each checkRDAP, DNS, email, CT logs, HTTP, TLS, RIPEstat and InternetDB
recon_batchup to ten domain reports, with three running at a time and source failures kept in each reportpublic APIs + DNS; direct checks are optional
compare_domainsshared IPs, nameservers, mail servers and registrars, with the records behind each matchDNS + RDAP
investigate_sitepage details, displayed company IDs, legal/contact pages, registration, archive captures, HTTP and TLS, with concrete signals and missing checkswebsite + public sources
certificate_historycertificate issuers, validity dates, related names and links to the CT entriescrt.sh
domain_whoisregistrar, created/expires, nameservers, abuse contactRDAP (rdap.org)
ip_whoisnetwork owner, CIDR, country, abuse contact, PTRRDAP + reverse DNS
dns_lookupA, AAAA, CNAME, MX, NS, TXT, SOA, CAA (or pick your own)your resolver or a custom one
subdomainssubdomains found in certificate transparency logscrt.sh
waybackarchived snapshots of a URL, supports example.com/*Wayback CDX API
http_headersstatus, redirect chain, headers, missing security headersdirect request
shodan_internetdbopen ports, hostnames, CPEs, known CVEsShodan InternetDB (free)
email_securitySPF, DMARC, MTA-STS, TLS-RPT, DKIM, graded A-FDNS
tls_certificateissuer, expiry, SANs, TLS version, why a cert is invaliddirect connection
asn_lookupwhich AS announces an IP, who owns it, all its prefixesRIPEstat

http_headers, tls_certificate and investigate_site contact the site directly. email_security can fetch its MTA-STS policy. recon_domain includes these direct checks by default; set include_active=false to skip HTTP, TLS and the MTA-STS policy fetch.

recon_batch starts with direct checks off. compare_domains uses public APIs and DNS only. DNS lookups still involve resolvers and may reach the domain's authoritative nameservers. There are no port scans, directory brute forcing, form submissions or browser scripts.

Investigations

For a single domain, start with recon_domain. Its coverage field says which checks succeeded, failed, returned partial data or were skipped. A broken source leaves an error in that section; it does not erase the other results. IPv4 and IPv6 addresses are both considered, with details for at most three addresses.

For a portfolio or a list of domains, use recon_batch. It accepts up to ten entries, removes duplicate hostnames and limits work to three domains at a time. Each domain has a 90 second deadline. incomplete_domains makes failures easy to find. Subdomain history and direct connections are both off by default.

For possible links between sites, use compare_domains. It reports shared infrastructure, not a common-owner verdict. A CDN address, Google mail server or popular registrar can appear on thousands of unrelated domains. Failed DNS and RDAP checks stay visible rather than being treated as a clean result.

For a website or shop that needs checking, use investigate_site. It reads the supplied page and, optionally, up to three linked contact/legal pages on the same origin. It extracts the title, description, displayed company identifiers, form destinations and linked domains, then combines those details with the public lookups. HTML is read as text; scripts, forms and linked assets are never executed.

The report has signals, each pointing to its evidence, and an unavailable list. Its assessment is either signals_collected or incomplete. Neither means the site is safe. It cannot confirm deliveries, reviews, products or ownership of a company number. A number copied into a footer is only an observed claim, not a verified registration.

An optional reference_domain compares the spelling against a domain you already trust. Public suffixes, including private suffixes such as github.io, come from the package's bundled list without a download. Similar spelling is a reason to check the URL, not proof of impersonation.

certificate_history reads issuance records from crt.sh and reports duplicate IDs and truncation. It does not tell you which certificate is served now; use tls_certificate for that.

Sources and freshness

MCP results include checked_at, an evidence list and a notice that external text is untrusted data. Evidence records contain the source URL, response status, collection time and whether the response came from cache. DNS evidence identifies the queried name and resolver type.

checked_at is the report time. fetched_at is when this tool obtained the source response, not when the provider last updated its underlying data. Cached responses retain their earlier collection time and expiry. Cache entries made before 0.3.0 have an unknown collection time until fetched again.

Records, page titles and other external strings can contain misleading text or instructions. They are evidence to inspect, never instructions for the connected agent. The final interpretation still belongs to the investigator.

Direct requests accept public HTTP/HTTPS destinations only. Private, local, multicast and reserved addresses are blocked, including redirect destinations. Connections use a checked DNS address while preserving the hostname for HTTP and TLS. HTTP headers are read without downloading the final page body. JSON responses are limited to 8 MiB; site pages to 512 KiB; MTA-STS policies to 64 KiB. Legal-page redirects cannot leave the original origin. Environment proxies are not used.

Install

Needs Python 3.10+.

pip install osint-mcp-server

or if you use uv you don't need to install anything, just point the client at uvx (see below).

Claude Desktop

Add this to claude_desktop_config.json:

{

"mcpServers": { "osint": { "command": "uvx", "args": ["osint-mcp-server"] } } }

If you installed with pip, "command": "osint-mcp-server" with no args works too.

Claude Code
claude mcp add osint -- uvx osint-mcp-server

Cursor, Windsurf etc. take the same JSON as Claude Desktop.

Updating

For a pip installation:

python -m pip install --upgrade osint-mcp-server

For a client that launches uvx, use osint-mcp-server@latest in args when you want uv to check for the latest package. Use osint-mcp-server@0.3.0 to pin this release. Restart the MCP server after updating. Existing pip installations do not update themselves.

Allow at least 120 seconds for individual investigations and 360 seconds for a full batch in clients with configurable tool timeouts. crt.sh and Wayback can take longer after retries; use the smaller tools when you only need one answer.

Example prompts

  • "run recon on example.com and tell me what stands out"
  • "can someone spoof email from our domain? what should we fix first?"
  • "which of these 20 domains have certificates expiring this month?"
  • "what ip ranges does AS13335 announce?"
  • "check the security headers on these 5 sites and tell me which are worst"
  • "which of the subdomains of example.com resolve to something with open ports?"
  • "what did example.com/about look like in 2015?"
  • "compare these three shops: do they share hosting, mail servers or a registrar? show the actual matches"
  • "investigate this shop URL, include the contact pages, and tell me which checks couldn't finish"
  • "does examp1e.com resemble example.com? collect the evidence without calling it a scam"
  • "run recon on these ten domains without connecting to their websites"
  • "show the last twenty certificate entries for this domain and which names they contain"

Caching

API responses (RDAP, crt.sh, Wayback, RIPEstat, InternetDB) are cached in sqlite for 6 hours at ~/.cache/osint-mcp/cache.sqlite3, mostly so crt.sh doesn't get hammered. DNS, TLS and HTTP checks are always live.

OSINT_MCP_CACHE=off           # disable

OSINT_MCP_CACHE_TTL=3600 # seconds OSINT_MCP_CACHE_PATH=/tmp/x.db

Notes

  • crt.sh and the Wayback CDX API are slow and return 502/503 pretty often. The server retries a couple of times; an individual request can take up to three minutes after retries. A batch domain stops after 90 seconds instead.
  • InternetDB isn't real-time and only has IPs Shodan has actually scanned.
  • DKIM selectors can't be listed, email_security tries the common ones. Pass dkim_selectors if you know yours.
  • Some TLDs return no RDAP data through rdap.org. A missing response does not establish that the domain is unregistered.
  • Site checks read server-rendered HTML. Content loaded only by JavaScript will not appear. The tool does not bypass bot blocks or log in.

Development

git clone https://github.com/robyroro/osint-mcp

cd osint-mcp pip install -e . pytest ruff build ruff check src tests pytest python -m build

Tests use synthetic data and mocked network responses. They include a real MCP stdio handshake, source failures, cache migration, bounded batches and blocked network destinations. CI runs Python 3.10, 3.12 and 3.14 on Linux and Windows.

The publishing workflow runs on v* tags. It checks the version, runs tests, builds the package, publishes to PyPI and then updates the official MCP Registry. A GitHub push alone does not update an installed package or a directory's description.

To poke at it with the MCP inspector:

npx @modelcontextprotocol/inspector osint-mcp

Be reasonable

This only pulls public data, but still: use it on your own stuff, bug bounty targets that are in scope, or for research. Don't use it to go after people.

License

MIT © Robert Vind-Gardoș (@robyroro)

Ask PopNx