# IPs-LE [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/nolindnaidoo/ips-le  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ips-le

## Description
Extract every IP address, CIDR block and MAC, normalized and classified by scope.

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

```json
"mcpServers": {
  "ips-le": {
    "command": "npx",
    "args": ["-y","ips-le-mcp"]
  }
}
```

## Documentation

## What IPs-LE MCP server does

The IPs-LE MCP server extracts four address types from text: IPv4, IPv6, CIDR blocks, and MAC addresses. Each finding includes its original text, normalized representation, kind, and classification. IPv6 normalization follows RFC 5952, so equivalent spellings are returned in one canonical form.

Classifications cover loopback, private, link-local, carrier-grade NAT, multicast, broadcast, documentation, unique-local, reserved, and global ranges. IPv4-mapped IPv6 values inherit the corresponding IPv4 classification. CIDR results also include the prefix length, network, final address, IPv4 broadcast address where applicable, and address count.

The IPs-LE MCP server reports where a value occurs when the input format provides structure, including line, column, and keys from JSON, YAML, TOML, INI, dotenv, and CSV. It can still scan other text formats, but those results do not include a key path.

## How it works

The MCP package exposes an `extract_ips` tool over standard input and output. An agent sends document text to the tool, and the server returns extracted findings and refusals for values it cannot interpret safely. Processing is local and based on address syntax, bit arithmetic, and defined registries.

Ambiguous or invalid forms are reported instead of being silently converted. Examples include leading-zero IPv4 octets, shortened numeric forms such as `10.0.1`, integer address notation, malformed IPv6, out-of-range CIDR prefixes, and unseparated MAC strings. A strict pipeline can use the documented strict behavior to stop when unresolved ambiguity is present.

The IPs-LE MCP server does not resolve DNS, query geolocation or ASN services, perform WHOIS or reachability checks, send telemetry, rewrite files, or decide whether an address belongs in a policy.

## Setup and configuration

Install and run the Node-based server with:

```bash
npx ips-le-mcp
```

The package is intended for MCP agents that can launch a standard stdio server. No environment variables or network credentials are specified. The README also documents separate editor, Rust CLI, and workspace-scanning forms of IPs-LE, but those are distinct from the MCP interface.

## Tools and capabilities

- `extract_ips`: scan supplied text for IPv4, IPv6, CIDR, and MAC values.
- Normalize IPv6 addresses according to RFC 5952.
- Classify addresses by defined scope or registry category.
- Return source locations and structured keys when available.
- Include CIDR network arithmetic and decimal address counts.
- Preserve ambiguous inputs as named findings rather than guessing.

## Limitations and notes

The MCP material identifies one tool, `extract_ips`; it does not describe workspace scanning through MCP. Results depend on the text supplied by the client. The server does not read unsaved editor state or files through this interface unless the client provides their contents.

MAC extraction is subject to the server’s ambiguity rules, and some numeric or malformed address forms are intentionally refused. Classification is not a policy verdict: a `private`, `global`, or other label describes the address range, not whether the value should be allowed.

_Full upstream README: https://allmcps.com/mcp/ips-le/readme_