ipv4.fr Network Tools
REMOTE · IPV4.FR
DNS, WHOIS, SSL, IP geolocation, email validation, DNSBL blacklist, HTTP headers, subnet calc.
Available components
Last scanned (7 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 470 tokens (~52/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 25 Oct 26 0
- Schema quality: 44 → 52 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “domain_audit” functional
- 24 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://ipv4.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ipv4.fr | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f1a1ab078543919913f5088dd4a69a9b |
| SANs: ipv4.fr, *.ipv4.fr | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of ipv4.fr. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| ipv4.fr. | DS published | 2371 | 13 | Verified |
| ipv4.fr. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ipv4.fr/mcp | Verified | 200 | |
| http (plaintext) | http://ipv4.fr/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dns_lookup ~56
DNS records for a domain (A, AAAA, MX, TXT, NS by default; also CNAME, SOA).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. example.com |
| types | array | – | – |
No output schema declared.
No examples provided.
domain_audit ~111
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. example.com |
No output schema declared.
No examples provided.
email_validate ~36
Validate an email address: syntax, MX records, SMTP check, disposable and role-based detection.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address |
No output schema declared.
No examples provided.
http_headers ~44
HTTP response headers and status of a public URL (HEAD request, redirects followed and checked).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or domain, e.g. https://example.com |
No output schema declared.
No examples provided.
ip_blacklist ~43
Check an IPv4 address against 3 DNS blacklists (Barracuda, SpamCop, UCEPROTECT).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 address |
No output schema declared.
No examples provided.
ip_geolocation ~39
Geolocation of an IP address: country, city, ISP, coordinates, timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address |
No output schema declared.
No examples provided.
ssl_check ~44
TLS certificate of a host: validity, issuer, expiry, days remaining, SAN.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname or public IP |
| port | integer | – | – |
No output schema declared.
No examples provided.
subnet_calc ~56
IPv4 subnet calculator from CIDR: network, broadcast, netmask, wildcard, host range, host count.
| Name | Type | Req | Description |
|---|---|---|---|
| cidr | string | yes | CIDR notation, e.g. 192.168.1.0/24 |
No output schema declared.
No examples provided.
whois ~41
WHOIS registration data for a domain: registrar, creation and expiry dates, name servers.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. example.com |
No output schema declared.
No examples provided.
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.
remote · ipv4.fr
claude mcp add --transport http fr-ipv4-network-tools 'https://ipv4.fr/mcp'
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.