ipdata MCP by usefulapi
Look up location, network, company and threat data for IP addresses and ASNs in ipdata.
作者による説明(英語の原文)
Domain and website investigations: batch recon, shared infrastructure, CT history and public lookups
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
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/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"osint": {
"command": "uvx",
"args": [
"osint-mcp-server"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"osint": {
"type": "stdio",
"command": "uvx",
"args": [
"osint-mcp-server"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント robyroro で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.3.0)がレジストリに届いたのは33 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにPython (uv)も必要です。
同じカテゴリには:ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi, Lambda Labs MCP by usefulapi
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Look up location, network, company and threat data for IP addresses and ASNs in ipdata.
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
| tool | what it does | source |
|---|---|---|
recon_domain | domain overview, highlights and coverage for each check | RDAP, DNS, email, CT logs, HTTP, TLS, RIPEstat and InternetDB |
recon_batch | up to ten domain reports, with three running at a time and source failures kept in each report | public APIs + DNS; direct checks are optional |
compare_domains | shared IPs, nameservers, mail servers and registrars, with the records behind each match | DNS + RDAP |
investigate_site | page details, displayed company IDs, legal/contact pages, registration, archive captures, HTTP and TLS, with concrete signals and missing checks | website + public sources |
certificate_history | certificate issuers, validity dates, related names and links to the CT entries | crt.sh |
domain_whois | registrar, created/expires, nameservers, abuse contact | RDAP (rdap.org) |
ip_whois | network owner, CIDR, country, abuse contact, PTR | RDAP + reverse DNS |
dns_lookup | A, AAAA, CNAME, MX, NS, TXT, SOA, CAA (or pick your own) | your resolver or a custom one |
subdomains | subdomains found in certificate transparency logs | crt.sh |
wayback | archived snapshots of a URL, supports example.com/* | Wayback CDX API |
http_headers | status, redirect chain, headers, missing security headers | direct request |
shodan_internetdb | open ports, hostnames, CPEs, known CVEs | Shodan InternetDB (free) |
email_security | SPF, DMARC, MTA-STS, TLS-RPT, DKIM, graded A-F | DNS |
tls_certificate | issuer, expiry, SANs, TLS version, why a cert is invalid | direct connection |
asn_lookup | which AS announces an IP, who owns it, all its prefixes | RIPEstat |
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.
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.
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.
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).
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 mcp add osint -- uvx osint-mcp-server
Cursor, Windsurf etc. take the same JSON as Claude Desktop.
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.
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
email_security tries the common ones. Pass dkim_selectors if you know yours.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
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.
MIT © Robert Vind-Gardoș (@robyroro)