Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer
FindIP
Overview
Description from the maker (original English)
IP intelligence lookups and FindIP Shield visitor risk signals for AI assistants.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 40/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: FINDIP_API_KEY, FINDIP_SHIELD_SECRET_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
FINDIP_API_KEY,FINDIP_SHIELD_SECRET_KEY
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"findip": {
"command": "npx",
"args": [
"-y",
"@findip/mcp"
],
"env": {
"FINDIP_API_KEY": "your-value",
"FINDIP_SHIELD_SECRET_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add findip --env FINDIP_API_KEY=your-value --env FINDIP_SHIELD_SECRET_KEY=your-value -- npx -y @findip/mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"findip": {
"command": "npx",
"args": [
"-y",
"@findip/mcp"
],
"env": {
"FINDIP_API_KEY": "your-value",
"FINDIP_SHIELD_SECRET_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"findip": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@findip/mcp"
],
"env": {
"FINDIP_API_KEY": "your-value",
"FINDIP_SHIELD_SECRET_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Your FindIP API key (free at https://www.findip.net). Used for IP lookups and your Shield sites.
- A Shield site's secret key (sec_...). Only needed for verify_session.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account findip-net, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18486 servers in this category
- Published to the registry more recently than 62% of the other 18486 servers in this category
- Basic checks equal to or better than 100% of the other 18486 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is FindIP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: FINDIP_API_KEY, FINDIP_SHIELD_SECRET_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 28 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Compose Preview Catalogs
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud✓ desktopcommander.app
Compose Preview Catalogs
Browse, inspect and render Jetpack Compose Material 3 and Wear component catalogs.
Runs in the cloud
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
| Tool | What it does | Key |
|---|---|---|
lookup_ip | Country, city, ISP and ASN for an IP, plus risk signals: VPN, proxy, Tor, relay, hosting, scanner, malicious listings, threat score | API key |
verify_session | Server-side risk check for a Shield session: score, recommendation, challenge status, IP and network rotation | Site secret key |
list_shield_sites | Your Shield sites with today's event and risky-event counts | API key |
recent_risky_events | Recent high-risk events on a site, for example "what risky traffic hit my signup form this week" | API key |
explain_event | One event in plain language: where it came from, which signals fired, what was recommended | API 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/mcpClaude 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
| Variable | Purpose |
|---|---|
FINDIP_API_KEY | Your FindIP API key. Required for lookup_ip, list_shield_sites, recent_risky_events and explain_event. |
FINDIP_SHIELD_SECRET_KEY | Secret key (sec_...) of one Shield site. Required for verify_session. Find it in the site's settings in the Shield dashboard. |
FINDIP_SHIELD_ACCOUNT_API | Set 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_MS | Request timeout. Default 15000. |
FINDIP_API_BASE_URL, FINDIP_SHIELD_BASE_URL, FINDIP_PORTAL_BASE_URL | Override 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.netandwww.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 installnpm run typecheck npm test # vitest, all HTTP mocked npm run build
License
MIT