
OSINT
io.github.robyroro由 GitHub 账号 robyroro 发布v0.3.0更新于 Oct 27, 2026
Domain and website investigations: batch recon, shared infrastructure, CT history and public lookups
发布方自己的服务:osint.foundation
概览
本地运行的 OSINT 类 MCP 服务器,用于域名与网站调查:批量侦察、WHOIS/RDAP、DNS、证书、存档与基础设施比对。
- 可以做什么
- 对单个域名做完整侦察,并给出每项检查的覆盖情况;或批量处理最多十个域名并标出失败项
- 比对多个域名共享的 IP、名称服务器、邮件服务器与注册商
- 检查网站页面信息、页面标注的公司编号、法律/联系页面、存档快照、HTTP 与 TLS
- 查询注册与网络数据:域名与 IP 的 WHOIS、DNS 记录、子域名、ASN 前缀
- 检查证书、存档快照、HTTP 头、开放端口与已知漏洞,以及邮件安全配置评级
- 适用场景
- 适合在信任某个域名、IP 或可疑网店之前做核查,审计自有域名的邮件与 TLS 配置,或比较一批域名的托管与邮件基础设施。它只收集公开证据,结论仍由使用者判断。
- 运行要求
- 以本地 Python 包形式运行(需 Python 3.10 及以上),可用 pip 或 uvx 启动;无需 API 密钥或账号。需要访问 RDAP、crt.sh、Wayback、RIPEstat、Shodan InternetDB 等公开来源的网络。可选环境变量 OSINT_MCP_CACHE、OSINT_MCP_CACHE_TTL、OSINT_MCP_CACHE_PATH 用于调整本地 sqlite 缓存。建议放宽工具超时(单次调查约 120 秒,批量约 360 秒)。
安装
在 SourceWeft 中
- 打开 控制台中的 OSINT,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
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
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+.
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:
If you installed with pip, "command": "osint-mcp-server" with no args works too.
Claude Code
Cursor, Windsurf etc. take the same JSON as Claude Desktop.
Updating
For a pip installation:
For a client that launches uvx, use osint-mcp-server@latest in args when you want uv to check for the latest package. Use [email protected] 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.
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_securitytries the common ones. Passdkim_selectorsif 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
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:
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)
来源:README.md,提交 815276a
工具
0版本历史
4- v0.3.0最新Oct 5, 2026
- v0.2.2Oct 1, 2026
- v0.2.1Sep 30, 2026
- v0.2.0Sep 26, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Osint 集成
osint.foundation
foundation.osint官方发布者
OSINT查询:用户名、社交资料、电话、域名、IP、加密钱包和公司。AI 翻译

OSINT.SX
由 GitHub 账号 osintsx 发布
让助手调用 OSINT.SX 进行人员与账号查询:一次跨全部来源搜索,另有 Google、微软、Epic、X、Steam、Instagram 和 TikTok 工具。

Domain Osint Mcp
由 GitHub 账号 robertoyanguas-ops 发布
一个远程 MCP 服务器,让助手执行域名 OSINT 检查:实时 DNS 解析、TLS 证书信息和 HTTP 安全评级。

Robin: AI-Powered Dark Web OSINT
由 GitHub 账号 apurvsinghgautam 发布
Robin 通过 Tor 执行暗网 OSINT 调查,让助手搜索洋葱搜索引擎、抓取页面并用代理自身的模型保存报告。

UPI ID OSINT - Phone to UPI VPAs + Bank Names (India)
由 GitHub 账号 AnshumanAtrey 发布
托管在 Apify 上的 OSINT 工具,可将印度手机号或 UPI VPA 映射为活跃 UPI ID 及 NPCI 登记的银行户名。