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