# IPs-LE (npm · ips-le-mcp)

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

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `ips-le-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/nolindnaidoo-ips-le/ips-le-mcp.md), [page](https://verifymcp.io/servers/nolindnaidoo-ips-le/ips-le-mcp)

## Channel facts

- Registry: `npm`
- Package: `ips-le-mcp`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 295 tokens (~295/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the IPs-LE MCP server?

IPs-LE runs locally as an npm package, launched with npx -y ips-le-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add nolindnaidoo-ips-le -- npx -y ips-le-mcp
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add nolindnaidoo-ips-le -- npx -y ips-le-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nolindnaidoo-ips-le": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ips-le-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nolindnaidoo-ips-le --command npx --arg -y --arg ips-le-mcp
```

### Hermes

```yaml
mcp_servers:
  nolindnaidoo-ips-le:
    command: "npx"
    args: ["-y", "ips-le-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "nolindnaidoo-ips-le": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "ips-le-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nolindnaidoo-ips-le -t stdio -c npx -a -y ips-le-mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 78, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-20 (score 77, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 75, +36)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.37
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-12 (score 39, 0)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (1)

### `extract_ips` (~295 tokens)

Extract every IP address, CIDR block and MAC address from a document, normalized and classified. IPv6 is canonicalized per RFC 5952, so 2001:0db8::0001 and 2001:db8::1 come back as one address rather than two. Each finding carries its line, column and — for JSON, YAML, TOML, INI, dotenv, CSV and logs — the key it sits under. Text this cannot read unambiguously is returned as a named refusal, never as a guess: a leading zero (octal or decimal, depending on the resolver), a dotted triple that may be a version, a bare integer in an address field. Resolves no names, geolocates nothing, opens no sockets.

Input parameters:

- `class` (array): Report only these classes. Refusals are always reported.
- `content` (string, required): The document text to scan.
- `filename` (string): Filename used to infer the format when `format` is absent, e.g. "app.yaml" or "access.log".
- `format` (string): Document format. Optional — it only decides whether findings carry a key path, never whether they are found.
- `kind` (array): Report only these kinds. Refusals are always reported.
- `maxResults` (integer): Cap on returned findings (default 500). meta.truncated reports whether any were dropped.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nolindnaidoo-ips-le/ips-le-mcp#diagnostics

## Score history

- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 39
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-11: 39
- 2026-10-04: 70

## Common questions

### What is the IPs-LE MCP server?

IPs-LE is an MCP server listed in the public MCP registry as io.github.nolindnaidoo/ips-le. Extract every IP address, CIDR block and MAC, normalized and classified by scope. This page covers its npm package (ips-le-mcp).

### Is the IPs-LE MCP server safe to use?

IPs-LE scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the IPs-LE MCP server expose?

IPs-LE exposes 1 tool: extract_ips. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.

### Is the IPs-LE MCP server still maintained?

IPs-LE is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the IPs-LE MCP server under?

IPs-LE declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/ips-le-mcp
- Socket report: https://socket.dev/npm/package/ips-le-mcp
- Repository: https://github.com/nolindnaidoo/ips-le
- Website: https://letools.dev/tools/ips-le
- Changelog RSS feed: https://verifymcp.io/servers/nolindnaidoo-ips-le/ips-le-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nolindnaidoo-ips-le/ips-le-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nolindnaidoo-ips-le/ips-le-mcp