# ipfind/ipfind-mcp-server [Health: Active]

**Category:** 🗺️ Location Services  
**Repository:** https://github.com/ipfind/ipfind-mcp-server  
**GitHub Stars:** 3  
**npm Downloads (last month):** 57  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ipfind-ipfind-mcp-server

## Description
IP Address location service using the IP Find API

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ipfind-mcp-server": {
    "command": "npx",
    "args": ["-y","@ipfind/ipfind-mcp-server"],
    "env": {
      "IPFIND_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `IPFIND_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What ipfind/ipfind-mcp-server MCP server does

The ipfind/ipfind-mcp-server MCP server connects an MCP-compatible AI assistant to IP Find’s IP address location service. It gives the assistant a way to request location information for IP addresses through the IP Find API.

This is intended for workflows where an assistant needs to use IP-based location data as part of a conversation or task. The provided material does not specify the individual response fields, supported IP address formats, lookup limits, or whether the service supports additional IP Find operations beyond location lookup.

## How it works

The project runs as an MCP server on the local machine. An MCP client starts it with Node.js using the package published as `@ipfind/ipfind-mcp-server`. The server then uses the configured IP Find API key when connecting to the external API.

The README documents Claude Desktop as the client example. Its configuration places the server under the `mcpServers` section and supplies the launch command, package arguments, and environment variable. The assistant can then use the server to get locations for IP addresses.

## Setup and configuration

Install or run the server through `npx`, which requires Node.js to be available. Add an entry like this to the MCP client configuration:

```json
{
  "mcpServers": {
    "ipfind": {
      "command": "npx",
      "args": ["-y", "@ipfind/ipfind-mcp-server"],
      "env": {
        "IPFIND_API_KEY": "your-api-key"
      }
    }
  }
}
```

Replace the example value with an API key generated through IPfind.com. The key is passed to the process as `IPFIND_API_KEY`; without that credential, the documented API connection cannot be configured. You also need an MCP client, such as the Claude Desktop app, to start and use the server.

## Tools and capabilities

The documented capability is IP address location lookup through IP Find. In practical terms, an assistant can send an IP address to the MCP server and receive location data returned by the IP Find API.

The supplied material does not list tool names, schemas, geographic fields, bulk lookup support, caching, or controls for request behavior. Those details should be confirmed from the package or API documentation before building against a specific interface.

## Limitations and notes

The server depends on an external IP Find API and requires an IP Find API key. The README does not state whether the key is free, paid, rate-limited, or subject to usage quotas, so pricing and service limits cannot be determined from the supplied information.

The README explicitly shows Claude Desktop as an MCP client example, but it does not document setup instructions for other clients. It also does not describe error handling, privacy behavior, accuracy, IPv4 or IPv6 coverage, or the retention of submitted addresses. Treat those areas as unknown until verified with IP Find.

For an assistant that needs only IP-based location access, the ipfind/ipfind-mcp-server MCP server provides a focused MCP connection to the IP Find API rather than a general location platform.

_Full upstream README: https://allmcps.com/mcp/ipfind-ipfind-mcp-server/readme_