原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

OSINT

作者:robyroro版本 0.3.0i★ –i在你的电脑上运行
注册名称io.github.robyroro/osint-mcp

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 网络安全

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 robyroro 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“网络安全”中的其他服务器比较i

  • 星标数多于此分类中其他 996 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 996 个服务器的 57% 更新
  • 基础检查结果等于或优于此分类中其他 996 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

OSINT 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.0)于33天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Action1 MCP by usefulapi, QNSQY, EchelonGraph CVE & Exposure

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Read endpoints, missing updates, CVE vulnerabilities, installed software and reports in Action1.

在云端运行今天更新
安装

QNSQY

作者:quantumsequrity

Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets

在你的电脑上运行今天更新
安装

EchelonGraph CVE & Exposure

作者:echelongraph

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

电脑或云端今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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)

问 PopNx