# Ip Address Lookup — REST API endpoint `ip-address-lookup`

Return geolocation and network details for a public IPv4 or IPv6 address: country, region, city, postal code, coordinates, timezone, ASN and organization, currency and calling code.

- Category: network
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/ip-address-lookup/execute (no API keys, 60 req/min per IP)
- Network tool: fetches a fixed, hard-coded public upstream (never a private host).
- Reference page: https://findutils.com/api/ip-address-lookup/
- Same tool on the other surface: https://findutils.com/mcp/ip-address-lookup/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/ip-address-lookup/execute \
  -H "Content-Type: application/json" \
  -d '{
    "ip": "8.8.8.8"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/ip-address-lookup
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `ip` | string | yes | Public IPv4 or IPv6 address, e.g. "8.8.8.8" or "2606:4700::1111". |

Example arguments (verified):

```json
{
  "ip": "8.8.8.8"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:ip_address_lookup`. Full MCP reference: https://findutils.com/mcp/ip-address-lookup/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt