
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 的遠端 MCP 伺服器,可依印度手機號碼或 UPI VPA 查詢活躍的 UPI ID 及 NPCI 登記的銀行戶名。