FindIP

io.github.findip-net由 GitHub 帳號 findip-net 發布v0.1.1更新於 Oct 24, 2026

IP intelligence lookups and FindIP Shield visitor risk signals for AI assistants.

發布方自己的服務：FindIP

已驗證STDIO僅桌面網頁搜尋與抓取安全與監控

概覽

AI 產生的概覽

一個本機 MCP 伺服器，讓 AI 助理查詢 FindIP 的 IP 情報與 FindIP Shield 訪客風險訊號。

可以做什麼
查詢 IP 位址的國家、城市、ISP、ASN，以及 VPN、代理、Tor、主機代管、掃描器、威脅評分等風險訊號。在伺服器端驗證 Shield 工作階段的風險評分、建議、挑戰狀態與網路輪換。列出你的 Shield 網站及當日事件與風險事件數量。檢視網站近期高風險事件，並以白話說明單一事件。
適用情境
當你希望助理判斷某個 IP 或訪客工作階段是否有風險，或想在不離開對話的情況下檢視並解釋 FindIP Shield 網站近期的風險流量時適用。
執行需求
透過 npm 套件安裝，以 stdio 在本機執行，需要 Node.js 18.17 或更新版本。需在 FINDIP_API_KEY 提供 FindIP API 金鑰；verify_session 另需在 FINDIP_SHIELD_SECRET_KEY 提供 Shield 網站金鑰。需要連線至 FindIP 主機的網路。
安裝前請注意
需要兩組密鑰：FINDIP_API_KEY，以及用於工作階段驗證的 FINDIP_SHIELD_SECRET_KEY。伺服器會將 IP 與工作階段資料傳送給 FindIP。風險訊號描述的是連線而非特定個人，瀏覽器也可能被繞過，因此重要的放行、挑戰或封鎖決定應在自己的後端完成。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 FindIP，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

FindIP MCP server

Ask your assistant about an IP address or a risky session, and get the answer from FindIP.

@findip/mcp is a Model Context Protocol server for FindIP. It gives Claude, Cursor and other MCP clients IP intelligence and FindIP Shield risk signals. It runs locally over stdio and only reads data.

Tools

ToolWhat it doesKey
lookup_ipCountry, city, ISP and ASN for an IP, plus risk signals: VPN, proxy, Tor, relay, hosting, scanner, malicious listings, threat scoreAPI key
verify_sessionServer-side risk check for a Shield session: score, recommendation, challenge status, IP and network rotationSite secret key
list_shield_sitesYour Shield sites with today's event and risky-event countsAPI key
recent_risky_eventsRecent high-risk events on a site, for example "what risky traffic hit my signup form this week"API key
explain_eventOne event in plain language: where it came from, which signals fired, what was recommendedAPI key

All five tools are read-only. docs/BACKEND.md lists the FindIP endpoint behind each one.

Setup

You need Node.js 18.17 or later and a FindIP API key. Keys are free at findip.net.

Claude Code

bash
claude mcp add findip --env FINDIP_API_KEY=your_api_key -- npx -y @findip/mcp

Claude Desktop

Add this to claude_desktop_config.json (Settings, Developer, Edit Config), then restart Claude Desktop:

json
{  "mcpServers": {    "findip": {      "command": "npx",      "args": ["-y", "@findip/mcp"],      "env": {        "FINDIP_API_KEY": "your_api_key"      }    }  }}

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

json
{  "mcpServers": {    "findip": {      "command": "npx",      "args": ["-y", "@findip/mcp"],      "env": {        "FINDIP_API_KEY": "your_api_key"      }    }  }}

Configuration

VariablePurpose
FINDIP_API_KEYYour FindIP API key. Required for lookup_ip, list_shield_sites, recent_risky_events and explain_event.
FINDIP_SHIELD_SECRET_KEYSecret key (sec_...) of one Shield site. Required for verify_session. Find it in the site's settings in the Shield dashboard.
FINDIP_SHIELD_ACCOUNT_APISet to 0 to turn off the three Shield account tools, so the API key is used for IP lookups only. On by default.
FINDIP_TIMEOUT_MSRequest timeout. Default 15000.
FINDIP_API_BASE_URL, FINDIP_SHIELD_BASE_URL, FINDIP_PORTAL_BASE_URLOverride the FindIP hosts, for testing.

The Shield account tools allow 60 requests per account per minute. Repeated requests with a wrong key are blocked for 10 minutes.

Keys are read from the environment only. They are never accepted as tool arguments and never appear in tool output or error messages.

Examples

  • "Look up 203.0.113.9. Is it a VPN or a hosting provider?"
  • "Verify Shield session sess_8f2c and tell me why it was flagged."
  • "What risky traffic hit my signup form this week?"
  • "Explain event 5b1e... on shop.example. Should I worry?"

How to read the results

FindIP reports risk signals. A VPN, a hosting network or a high score tells you about the connection, not about the person behind it. Use the signals to decide who gets a closer look, an extra step or a manual review.

The Shield browser SDK collects signals and can add friction in the page, but a browser can be scripted or bypassed, so it is not a security boundary. Decisions that matter belong on your server: call server verification (the endpoint verify_session uses) from your backend before you allow, challenge or block. A session with risk_status: "unknown" had no IP intelligence; treat it as unknown, not as safe.

Privacy

  • The server talks only to FindIP: api.findip.net, shield.findip.net and www.findip.net.
  • Shield tools never return end-user identity (email, user ID and their hashes). FindIP removes it before the data leaves its servers.
  • Site listings are a short summary: no site keys, no settings.
  • No telemetry, and nothing is written to disk.

Development

bash
npm installnpm run typechecknpm test        # vitest, all HTTP mockednpm run build

License

MIT

來源：README.md，提交 4feccd4

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.1最新Oct 11, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Findip 整合

FindIP

ai.findip官方發布者

FindIP 是遠端 MCP 伺服器，讓助理依語意而非關鍵字搜尋、比較與分析專利。

Streamable HTTP可網頁執行驗證方式
知識與記憶需要憑證Oct 24, 2026