# ipv4.fr Network Tools (remote · ipv4.fr)

DNS, WHOIS, SSL, IP geolocation, email validation, DNSBL blacklist, HTTP headers, subnet calc.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `ipv4.fr`: 73/100 (this document), [markdown](https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4.md), [page](https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4)

## Channel facts

- Endpoint: `https://ipv4.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-06.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 470 tokens (~52/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 ipv4.fr Network Tools MCP server?

ipv4.fr Network Tools is a hosted endpoint at https://ipv4.fr/mcp, so there is nothing to install locally. 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 --transport http fr-ipv4-network-tools 'https://ipv4.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-ipv4-network-tools": {
      "url": "https://ipv4.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-ipv4-network-tools": {
      "type": "http",
      "url": "https://ipv4.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-ipv4-network-tools]
url = "https://ipv4.fr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-ipv4-network-tools": {
      "type": "remote",
      "url": "https://ipv4.fr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-ipv4-network-tools --url 'https://ipv4.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-ipv4-network-tools:
    url: "https://ipv4.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-ipv4-network-tools": {
      "Transport": "http",
      "Url": "https://ipv4.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-ipv4-network-tools -t streamable-http -u 'https://ipv4.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-ipv4-network-tools": {
      "type": "http",
      "url": "https://ipv4.fr/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-06 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-03 (score 72, +1)

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

### 2026-11-01 (score 71, +1)

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

### 2026-10-30 (score 70, +1)

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

### 2026-10-28 (score 69, +1)

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

### 2026-10-26 (score 68, +1)

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

### 2026-10-25 (score 67, 0)

- [functional regression] Schema quality: 44 → 52
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “domain_audit”

### 2026-10-24 (score 67)

First indexed and scored.

## MCP tools (9)

### `dns_lookup` (~56 tokens)

DNS records for a domain (A, AAAA, MX, TXT, NS by default; also CNAME, SOA).

Input parameters:

- `domain` (string, required): Domain name, e.g. example.com
- `types` (array)

### `whois` (~41 tokens)

WHOIS registration data for a domain: registrar, creation and expiry dates, name servers.

Input parameters:

- `domain` (string, required): Domain name, e.g. example.com

### `ssl_check` (~44 tokens)

TLS certificate of a host: validity, issuer, expiry, days remaining, SAN.

Input parameters:

- `host` (string, required): Hostname or public IP
- `port` (integer)

### `ip_geolocation` (~39 tokens)

Geolocation of an IP address: country, city, ISP, coordinates, timezone.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address

### `email_validate` (~36 tokens)

Validate an email address: syntax, MX records, SMTP check, disposable and role-based detection.

Input parameters:

- `email` (string, required): Email address

### `ip_blacklist` (~43 tokens)

Check an IPv4 address against 3 DNS blacklists (Barracuda, SpamCop, UCEPROTECT).

Input parameters:

- `ip` (string, required): IPv4 address

### `http_headers` (~44 tokens)

HTTP response headers and status of a public URL (HEAD request, redirects followed and checked).

Input parameters:

- `url` (string, required): URL or domain, e.g. https://example.com

### `subnet_calc` (~56 tokens)

IPv4 subnet calculator from CIDR: network, broadcast, netmask, wildcard, host range, host count.

Input parameters:

- `cidr` (string, required): CIDR notation, e.g. 192.168.1.0/24

### `domain_audit` (~111 tokens)

AI security audit of a domain: DNS, SPF, DMARC, TLS, HTTP security headers, WHOIS expiry and IP blacklists, returned as a 0-100 score, findings by severity and exact fixes. Requires a paid ipv4.fr API key (X-Api-Key header); uses 10 requests of the daily limit. Without a key, pay per call with x402 (0.05 USDC on Base).

Input parameters:

- `domain` (string, required): Domain name, e.g. example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4#diagnostics

## Score history

- 2026-11-06: 73
- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67

## Common questions

### What is the ipv4.fr Network Tools MCP server?

ipv4.fr Network Tools is an MCP server listed in the public MCP registry as fr.ipv4/network-tools. DNS, WHOIS, SSL, IP geolocation, email validation, DNSBL blacklist, HTTP headers, subnet calc. This page covers its hosted endpoint (https://ipv4.fr/mcp).

### Is the ipv4.fr Network Tools MCP server safe to use?

ipv4.fr Network Tools scores 73 out of 100 on VerifyMCP. 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 ipv4.fr Network Tools MCP server expose?

ipv4.fr Network Tools exposes 9 tools: dns_lookup, whois, ssl_check, ip_geolocation, email_validate, and 4 more. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.

### Does the ipv4.fr Network Tools MCP server require authentication?

No. We connected to ipv4.fr Network Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ipv4.fr Network Tools MCP server still maintained?

ipv4.fr Network Tools is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ipv4.fr Network Tools MCP server?

VerifyMCP ran 12 checks on ipv4.fr Network Tools, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ipv4.fr Network Tools: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ipv4.fr/mcp
- Website: https://ipv4.fr/
- Changelog RSS feed: https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4.json
- HTML version of this page: https://verifymcp.io/servers/fr-ipv4-network-tools/ipv4