Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HTTPfy network & DNS tools

REMOTE · HTTPFY.IO

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

Available components

+4 this week 78 Trust /100

Last scanned (32 minutes ago)

Scores higher than 72% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security77
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2105 tokens (~84/item across 25 items; 25 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (4% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 22 Nov 26 +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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • 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” functional
  • 16 Nov 26 +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.

  • 14 Nov 26 +1
    • 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 security
    • Schema quality: 60 → 72 ▼ functional
    • “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 cosmetic
  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 72

    First indexed and scored.

Diagnostics

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 22 Nov 2026 · Probed https://httpfy.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=httpfy.io CN=WE1,O=Google Trust Services,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA256 8518e5ee04d58217131470087c9f17d8
SANs: httpfy.io, *.httpfy.io
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 httpfy.io. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
httpfy.io. DS published 2371 13 Verified
httpfy.io. 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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://httpfy.io/mcp Verified 200
http (plaintext) http://httpfy.io/mcp HTTPS enforced 301 https://httpfy.io/mcp
MCP tools · 25 exposed · ~1,955 tokens

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 →

Tool Tokens
asn_lookup ~67

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.

NameTypeReqDescription
querystringyesIP address or ASN (8.8.8.8 or AS13335)

No output schema declared.

No examples provided.

bimi_check ~72

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.

NameTypeReqDescription
domainstringyesDomain (example.com)

No output schema declared.

No examples provided.

caa_check ~54

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

NameTypeReqDescription
domainstringyesDomain or hostname (www.example.com)

No output schema declared.

No examples provided.

certificate_transparency_search ~77

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).

NameTypeReqDescription
domainstringyesDomain (example.com)

No output schema declared.

No examples provided.

dkim_check ~77

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.

NameTypeReqDescription
domainstringyesDomain (example.com)
selectorstring–Selector (optional, blank = try common ones) (google)

No output schema declared.

No examples provided.

dmarc_check ~56

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.

NameTypeReqDescription
domainstringyesDomain (example.com)

No output schema declared.

No examples provided.

dns_lookup ~70

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

NameTypeReqDescription
domainstringyesDomain (Enter domain)
record_typestring–Select Record Type. Default: A

No output schema declared.

No examples provided.

dns_propagation_check ~114

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.

NameTypeReqDescription
domain_namestringyesDomain Name (Enter Domain Name)
query_typestring–Check Type. Default: Nameserver

No output schema declared.

No examples provided.

dns_report ~69

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.

NameTypeReqDescription
domainstringyesDomain (Enter domain)

No output schema declared.

No examples provided.

dnssec_check ~87

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.

NameTypeReqDescription
domainstringyesDomain (Enter domain to inspect)

No output schema declared.

No examples provided.

domain_expiry ~52

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

NameTypeReqDescription
domain_namestringyesDomain Name (Enter Domain Name)

No output schema declared.

No examples provided.

domain_health_report ~74

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.

NameTypeReqDescription
domainstringyesDomain (example.com)

No output schema declared.

No examples provided.

domain_whois ~57

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).

NameTypeReqDescription
domainstringyesDomain (Enter domain)

No output schema declared.

No examples provided.

ip_blacklist_check ~67

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.

NameTypeReqDescription
ip_addressstringyesIP Address (Enter IPv4 address)

No output schema declared.

No examples provided.

ip_whois ~59

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

NameTypeReqDescription
ip_addressstringyesIP Address (Enter IPv4 or IPv6 address)

No output schema declared.

No examples provided.

mac_vendor_lookup ~68

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

NameTypeReqDescription
mac_addressstringyesMAC Address (00:1A:2B:3C:4D:5E or 001a.2b3c.4d5e)

No output schema declared.

No examples provided.

mta_sts_check ~52

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

NameTypeReqDescription
domainstringyesDomain (example.com)

No output schema declared.

No examples provided.

mx_lookup ~64

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.

NameTypeReqDescription
domainstringyesDomain (Enter domain)

No output schema declared.

No examples provided.

ping ~57

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.

NameTypeReqDescription
hoststringyesHost (Enter host or IPv4 address)

No output schema declared.

No examples provided.

port_check ~63

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

NameTypeReqDescription
hoststringyesHost (example.com or 203.0.113.10)
portstringyesPort (443)

No output schema declared.

No examples provided.

report_feedback ~336

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.

NameTypeReqDescription
descriptionstringyesWhat you tried (tool and arguments), what happened (error text or the wrong part of the output) and what you expected.
impactstringyesblocked: could not finish. worked_around: finished another way. friction: finished, but it was harder than it should be.
kindstringyesmissing_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_fixstring–Optional: the concrete change that would have helped (new tool, argument, output field, wording).
taskstringyesShort phrase naming what the user asked for, e.g. 'check why mail from example.com goes to spam'.
tool_namestring–The httpfy tool the report is about. Leave out for missing_tool or general ideas.
NameTypeReqDescription
feedback_idstringyes–

No examples provided.

spf_lookup ~49

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

NameTypeReqDescription
domainstringyesDomain (Enter domain)

No output schema declared.

No examples provided.

spf_validate ~65

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.

NameTypeReqDescription
domainstringyesDomain (Enter domain)

No output schema declared.

No examples provided.

ssl_certificate_check ~81

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.

NameTypeReqDescription
domainstringyesDomain (Enter domain)

No output schema declared.

No examples provided.

traceroute ~68

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.

NameTypeReqDescription
hoststringyesHost (Enter host or IPv4 address)

No output schema declared.

No examples provided.

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.

remote · httpfy.io

# add to Claude Code
claude mcp add --transport http io-httpfy-httpfy 'https://httpfy.io/mcp'
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.