Back to Browse

Findip MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (3 strong, 2 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

7 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Your FindIP API key (free at https://www.findip.net). Used for IP lookups and your Shield sites.Required

Environment variable: FINDIP_API_KEY

A Shield site's secret key (sec_...). Only needed for verify_session.Required

Environment variable: FINDIP_SHIELD_SECRET_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-findip-net-findip-mcp": {
      "env": {
        "FINDIP_API_KEY": "your-findip-api-key-here",
        "FINDIP_SHIELD_SECRET_KEY": "your-findip-shield-secret-key-here"
      },
      "args": [
        "-y",
        "@findip/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

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:

{
  "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:

{
  "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

npm install
npm run typecheck
npm test        # vitest, all HTTP mocked
npm run build

License

MIT

Reviews

No reviews yet

Be the first to review this server!