# HTTPfy network & DNS tools (remote · httpfy.io)

Free DNS, SPF/DKIM/DMARC, TLS, WHOIS, IP/ASN, blocklist, ping, traceroute and port checks. No key.

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

## Components

- remote · `httpfy.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-httpfy-httpfy/httpfy.md), [page](https://verifymcp.io/servers/io-httpfy-httpfy/httpfy)

## Channel facts

- Endpoint: `https://httpfy.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-22.

- **Endpoint Security**: 77/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 is enforced; there's no plaintext access path.
  - 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2105 tokens (~84/item across 25 items; 25 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
  - Structured output schemas are declared (4% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the HTTPfy network & DNS tools MCP server?

HTTPfy network & DNS tools is a hosted endpoint at https://httpfy.io/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 io-httpfy-httpfy 'https://httpfy.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-httpfy-httpfy": {
      "url": "https://httpfy.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-httpfy-httpfy": {
      "type": "http",
      "url": "https://httpfy.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-httpfy-httpfy]
url = "https://httpfy.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-httpfy-httpfy": {
      "type": "remote",
      "url": "https://httpfy.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-httpfy-httpfy --url 'https://httpfy.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-httpfy-httpfy:
    url: "https://httpfy.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-httpfy-httpfy": {
      "Transport": "http",
      "Url": "https://httpfy.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-httpfy-httpfy -t streamable-http -u 'https://httpfy.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-httpfy-httpfy": {
      "type": "http",
      "url": "https://httpfy.io/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-22 (score 78, +1)

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

### 2026-11-20 (score 77, +1)

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

### 2026-11-18 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 72 → 84
- [functional] First check of Tool coverage: 4
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “report_feedback”

### 2026-11-16 (score 75, +1)

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

### 2026-11-14 (score 74, +1)

- [security] Tool “domain_whois” rewrote its description, which is the text the model reads
- [security] Tool “ip_blacklist_check” rewrote its description, which is the text the model reads
- [security] Tool “ip_whois” rewrote its description, which is the text the model reads
- [security] Tool “mx_lookup” rewrote its description, which is the text the model reads
- [security] Tool “spf_validate” rewrote its description, which is the text the model reads
- [security] Tool “ssl_certificate_check” rewrote its description, which is the text the model reads
- [security] Tool “traceroute” rewrote its description, which is the text the model reads
- [security] Tool “bimi_check” rewrote its description, which is the text the model reads
- [security] Tool “certificate_transparency_search” rewrote its description, which is the text the model reads
- [security] Tool “dns_propagation_check” rewrote its description, which is the text the model reads
- [security] Tool “dnssec_check” rewrote its description, which is the text the model reads
- [security] Tool “domain_expiry” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 60 → 72
- [cosmetic] “ip_blacklist_check” reworded the description of “ip_address”
- [cosmetic] “ip_whois” reworded the description of “ip_address”
- [cosmetic] “mac_vendor_lookup” reworded the description of “mac_address”
- [cosmetic] “ping” reworded the description of “host”
- [cosmetic] “traceroute” reworded the description of “host”
- [cosmetic] “dkim_check” made “selector” optional

### 2026-11-12 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 72)

First indexed and scored.

## MCP tools (25)

### `dns_lookup` (~70 tokens)

DNS record lookup

Look up DNS records of one type (A, AAAA, CNAME, MX, NS, SOA, TXT, SRV) for a domain using public resolvers.

Input parameters:

- `domain` (string, required): Domain (Enter domain)
- `record_type` (string): Select Record Type. Default: A

### `dns_propagation_check` (~114 tokens)

DNS propagation check

Query a domain's A or NS records on about 30 well-known public resolvers (all queried from httpfy.io's server; anycast resolvers answer from their nearest site) and report each resolver's answer, NXDOMAIN, NODATA or failure, to see whether a DNS change has propagated. CDN and GeoDNS names can legitimately differ between resolvers.

Input parameters:

- `domain_name` (string, required): Domain Name (Enter Domain Name)
- `query_type` (string): Check Type. Default: Nameserver

### `dnssec_check` (~87 tokens)

DNSSEC chain validation

Inspect a domain's DNSSEC chain from the root down: DS and DNSKEY records per zone, whether each DS matches a published key, signature expiry, and whether validating resolvers (Cloudflare, Google) treat the domain as secure, insecure or bogus. Signatures are judged by those resolvers, not recomputed.

Input parameters:

- `domain` (string, required): Domain (Enter domain to inspect)

### `mx_lookup` (~64 tokens)

MX records

List the mail exchanger (MX) records of a domain with their preferences, detect null MX (RFC 7505) and implicit MX, and flag MX targets that are CNAMEs, IP literals or do not resolve.

Input parameters:

- `domain` (string, required): Domain (Enter domain)

### `spf_lookup` (~49 tokens)

SPF record

Fetch the SPF record of a domain from its authoritative name server and list its mechanisms (ip4, ip6, include, redirect, all).

Input parameters:

- `domain` (string, required): Domain (Enter domain)

### `spf_validate` (~65 tokens)

SPF validation

Validate the SPF record of a domain: RFC 7208 syntax, single-record rule, DNS lookup count across includes and redirect (limit 10, a static estimate), void lookups, include loops and the all mechanism.

Input parameters:

- `domain` (string, required): Domain (Enter domain)

### `domain_whois` (~57 tokens)

Domain WHOIS

Registration data for a domain via RDAP (port-43 WHOIS as fallback): registrar, dates, status and name servers (personal contact data is redacted by registries).

Input parameters:

- `domain` (string, required): Domain (Enter domain)

### `domain_expiry` (~52 tokens)

Domain expiry date

Registration and expiry dates of a domain (RDAP, WHOIS fallback), with the time remaining before it expires or how long ago it expired.

Input parameters:

- `domain_name` (string, required): Domain Name (Enter Domain Name)

### `ssl_certificate_check` (~81 tokens)

SSL/TLS certificate check

Connect to a domain on port 443 and report a validity verdict (valid, expired, hostname mismatch, self-signed, untrusted, with the reason) plus the certificate chain: subject, SANs, issuer, validity dates, days remaining, TLS version and cipher. Revocation is not checked.

Input parameters:

- `domain` (string, required): Domain (Enter domain)

### `ping` (~57 tokens)

Ping from httpfy servers

Ping a public host from httpfy servers (4 ICMP echo requests) and report packet loss and round-trip times. Useful to test reachability from outside your own network.

Input parameters:

- `host` (string, required): Host (Enter host or IPv4 address)

### `traceroute` (~68 tokens)

Traceroute from httpfy servers

Traceroute to a public host from httpfy servers (up to 15 hops, one probe per hop; partial results are returned if the time limit is reached). Internal hops of httpfy's own network are masked.

Input parameters:

- `host` (string, required): Host (Enter host or IPv4 address)

### `ip_whois` (~59 tokens)

IP WHOIS

Registry data (RDAP) for a public IPv4 or IPv6 address: network range, holder organisation, abuse contact, registry and the announcing ASN.

Input parameters:

- `ip_address` (string, required): IP Address (Enter IPv4 or IPv6 address)

### `ip_blacklist_check` (~67 tokens)

IP blacklist (DNSBL) check

Check whether a public IPv4 address is listed on about 20 DNS-based blocklists such as Barracuda and SpamCop, showing listed, not listed or not checked (with the reason) per list.

Input parameters:

- `ip_address` (string, required): IP Address (Enter IPv4 address)

### `mac_vendor_lookup` (~68 tokens)

MAC address vendor lookup

Identify the manufacturer registered for a MAC address prefix (OUI) using the IEEE registry.

Input parameters:

- `mac_address` (string, required): MAC Address (00:1A:2B:3C:4D:5E or 001a.2b3c.4d5e)

### `asn_lookup` (~67 tokens)

ASN lookup

Look up the autonomous system (ASN) for a public IP address, or details for an ASN such as AS15169: name, country, announced prefixes and address counts.

Input parameters:

- `query` (string, required): IP address or ASN (8.8.8.8 or AS13335)

### `bimi_check` (~72 tokens)

BIMI record check

Check the BIMI record of a domain, whether DMARC meets BIMI requirements, the SVG logo (SVG Tiny PS checks) and the VMC/CMC certificate (validity dates, domain coverage, BIMI usage); the certificate chain is not verified.

Input parameters:

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

### `caa_check` (~54 tokens)

CAA record check

Find the CAA records that apply to a domain (climbing to parent domains per RFC 8659) and list which certificate authorities may issue certificates.

Input parameters:

- `domain` (string, required): Domain or hostname (www.example.com)

### `certificate_transparency_search` (~77 tokens)

Certificate transparency search

List certificates logged in Certificate Transparency for a domain (via crt.sh): issuer, validity window and names, with a summary by issuer. Source: crt.sh, with SSLMate Cert Spotter as a fallback when crt.sh is slow (Cert Spotter covers unexpired certificates only).

Input parameters:

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

### `dkim_check` (~77 tokens)

DKIM record check

Check DKIM public keys for a domain. With a selector it checks that selector; without one it probes common selectors. Reports key type and RSA key length and flags weak or revoked keys.

Input parameters:

- `domain` (string, required): Domain (example.com)
- `selector` (string): Selector (optional, blank = try common ones) (google)

### `dmarc_check` (~56 tokens)

DMARC record check

Find and explain the DMARC record of a domain (policy, pct, rua/ruf, alignment) and flag weaknesses such as p=none or missing external report authorization.

Input parameters:

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

### `dns_report` (~69 tokens)

Full DNS health report

Full DNS report for a domain: delegation from the root, every authoritative name server checked individually (reachability, recursion, TCP, consistency), SOA values, MX records and their reverse DNS, SPF, DMARC, DKIM and DNSSEC.

Input parameters:

- `domain` (string, required): Domain (Enter domain)

### `domain_health_report` (~74 tokens)

Domain health report card

Grade a domain A to F across 11 checks (name servers, SOA, DNSSEC, MX, SPF, DMARC, CAA, HTTPS certificate, HTTP to HTTPS redirect, HSTS, IPv6), with a reason and fix for each failed check.

Input parameters:

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

### `mta_sts_check` (~52 tokens)

MTA-STS and TLS-RPT check

Check MTA-STS (TXT record and the HTTPS policy file, mode and MX patterns) and the TLS-RPT reporting record for a domain.

Input parameters:

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

### `port_check` (~63 tokens)

TCP port check

Check whether one TCP port on a public host is open, closed or filtered when tested from httpfy servers on the internet.

Input parameters:

- `host` (string, required): Host (example.com or 203.0.113.10)
- `port` (string, required): Port (443)

### `report_feedback` (~336 tokens)

Report feedback to the httpfy team

Report a problem with this httpfy MCP server to the people who maintain it: a tool you needed that does not exist, a tool that failed or returned wrong or outdated data, or a tool or argument that was confusing. Use it only after an httpfy tool fell short, at most once per task, and keep working on the user's request afterwards. Say what you tried, what happened, what you expected, and if you can, the change that would fix it. Include the domain or IP the check was about when it matters, but no secrets, credentials or personal data. A human reads every report; no reply is sent. Not for testing the server or logging progress.

Input parameters:

- `description` (string, required): What you tried (tool and arguments), what happened (error text or the wrong part of the output) and what you expected.
- `impact` (string, required): blocked: could not finish. worked_around: finished another way. friction: finished, but it was harder than it should be.
- `kind` (string, required): missing_tool: no tool for what was needed. wrong_result: data looked wrong or outdated. error: the tool failed. confusing: unclear tool, argument or output. idea: anything else.
- `proposed_fix` (string): Optional: the concrete change that would have helped (new tool, argument, output field, wording).
- `task` (string, required): Short phrase naming what the user asked for, e.g. 'check why mail from example.com goes to spam'.
- `tool_name` (string): The httpfy tool the report is about. Leave out for missing_tool or general ideas.

Output parameters:

- `feedback_id` (string)

## Diagnostics

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

## Score history

- 2026-11-22: 78
- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72

## Common questions

### What is the HTTPfy network & DNS tools MCP server?

HTTPfy network & DNS tools is an MCP server listed in the public MCP registry as io.httpfy/httpfy. Free DNS, SPF/DKIM/DMARC, TLS, WHOIS, IP/ASN, blocklist, ping, traceroute and port checks. No key. This page covers its hosted endpoint (https://httpfy.io/mcp).

### Is the HTTPfy network & DNS tools MCP server safe to use?

HTTPfy network & DNS tools scores 78 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 HTTPfy network & DNS tools MCP server expose?

HTTPfy network & DNS tools exposes 25 tools: dns_lookup, dns_propagation_check, dnssec_check, mx_lookup, spf_lookup, and 20 more. Their descriptions and schemas cost roughly 1,955 tokens of context every time the server is loaded.

### Does the HTTPfy network & DNS tools MCP server require authentication?

No. We connected to HTTPfy network & DNS tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HTTPfy network & DNS tools MCP server still maintained?

HTTPfy network & DNS tools is still listed as active in the MCP registry. We last reached this channel on 22 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 HTTPfy network & DNS tools MCP server?

VerifyMCP ran 13 checks on HTTPfy network & DNS tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://httpfy.io/mcp
- Repository: https://github.com/cloudaidnet/httpfy.io
- Website: https://httpfy.io/agents
- Changelog RSS feed: https://verifymcp.io/servers/io-httpfy-httpfy/httpfy.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-httpfy-httpfy/httpfy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-httpfy-httpfy/httpfy.json
- HTML version of this page: https://verifymcp.io/servers/io-httpfy-httpfy/httpfy
