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.

io.github.dotmoosehosting/dotmoose-tools

REMOTE · MCP.DOTMOOSE.COM

Public DNS, mail, TLS, and web diagnostics plus Looking Glass probes via remote MCP.

Available components

60 Trust /100

Last scanned (1 hour ago)

Scores higher than 46% of remote servers

Reachable. Last reached 24 Oct 2026.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1910 tokens (~47/item across 40 items; 40 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "looking_glass_ping" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 41 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 24 Oct 26 60

    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 24 Oct 2026 · Probed https://mcp.dotmoose.com/tools/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.dotmoose.com CN=YE2,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 ECDSA 256 ECDSA-SHA384 6f6976660cf7ab46ab0deeb0ba1ef3a5ec2
SANs: auth.dotmoose.com, customer-api.dotmoose.com, mcp.dotmoose.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.dotmoose.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
dotmoose.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.dotmoose.com/tools/mcp Verified 200
http (plaintext) http://mcp.dotmoose.com/tools/mcp HTTPS enforced 308 https://mcp.dotmoose.com/tools/mcp
MCP tools · 40 exposed · ~1,758 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
audit_page_links ~47

Check up to 20 same-origin links found on one page and report the status of each. This is a single page check, not a site crawl.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

build_dmarc_record ~78

Assemble a DMARC record from a policy, optional subdomain policy, report addresses, and enforcement percentage.

NameTypeReqDescription
failureReportingstring––
percentinteger––
policystringyes–
ruaarray––
rufarray––
subdomainPolicystring––

No output schema declared.

No examples provided.

build_spf_record ~95

Assemble an SPF record from IP ranges, includes, and the a and mx mechanisms, and count its DNS lookup terms against the limit of 10.

NameTypeReqDescription
allQualifierstring––
includesarray––
ipv4array––
ipv6array––
redirectDomainstring––
useAboolean––
useMxboolean––

No output schema declared.

No examples provided.

calculate_bandwidth ~67

Convert a link speed into maximum daily and monthly transfer, convert monthly transfer into an average rate, and estimate how long a file transfer takes at a given rate.

NameTypeReqDescription
fileSizeGbnumber––
linkMbpsnumber––
monthlyTransferGbnumber––

No output schema declared.

No examples provided.

calculate_subnet ~41

Compute the network address, broadcast or last address, and address counts for an IPv4 or IPv6 CIDR block.

NameTypeReqDescription
cidrstringyes–

No output schema declared.

No examples provided.

check_bimi ~40

Read the BIMI record for a domain and selector. The selector defaults to default.

NameTypeReqDescription
domainstringyes–
selectorstring––

No output schema declared.

No examples provided.

check_compression ~37

Check whether a URL is served with gzip or Brotli compression and report the sizes with and without compression.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_dkim ~36

Read the DKIM public key record for a domain and selector.

NameTypeReqDescription
domainstringyes–
selectorstringyes–

No output schema declared.

No examples provided.

check_dmarc ~32

Read the DMARC record published at _dmarc for a domain.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_dns_propagation ~47

Check A, AAAA, MX, NS, and TXT answers for a hostname at the Cloudflare, Google, and Quad9 resolvers.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_dnssec ~39

Check the DS and DNSKEY records for a domain and whether a validating resolver sets the AD flag on its answers.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_domain_delegation ~38

List the delegation nameservers for a domain and the A and AAAA glue addresses for each one.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_favicon ~32

Locate the favicon a site declares and report its URL, type, and size.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_forward_confirmed_rdns ~40

Check the PTR record for an IP address and whether the name it returns resolves back to the same address.

NameTypeReqDescription
ipstringyes–

No output schema declared.

No examples provided.

check_http_chain ~31

Fetch a URL and return each redirect hop with status codes and response headers.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_http_status ~28

Fetch a URL and return the final status after following redirects.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_ip_blacklists ~38

Check an IP address, or the public addresses a hostname resolves to, against the reviewed DNS blacklist providers.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_ipv6_website ~34

Check whether a site answers over IPv6 and compare the result with IPv4.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_mta_sts ~35

Read the MTA-STS DNS record and the published policy file for a domain.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_mx_records ~36

List the MX records for a domain with the A and AAAA addresses of each mail server.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_page_metadata ~43

Return the title, meta description, canonical URL, headings, hreflang entries, and JSON-LD types found on a page.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_security_txt ~27

Fetch and parse the security.txt file for a site.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_smtp_starttls ~54

Connect to the mail servers for a domain on port 25 and report the banner, EHLO response, and STARTTLS support. No mail is sent and no recipient is tested.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_spf ~41

Read the SPF record for a domain and count the DNS lookup terms in the full include chain against the limit of 10.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_tls_certificate ~42

Connect to a host on port 443 and return the TLS version, cipher, and certificate details including expiry and subject alternative names.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_tls_configuration ~30

Observe which TLS protocol versions a host accepts and summarize its TLS configuration.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

check_tls_rpt ~33

Read the TLS-RPT record published at _smtp._tls for a domain.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_website_security ~41

Review the security controls a site exposes in its public responses, including security headers, cookie attributes, and CORS policy.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

estimate_backup_retention ~77

Estimate backup storage for a grandfather-father-son retention plan where weekly and monthly copies are full backups and daily copies are increments.

NameTypeReqDescription
dailyCopiesintegeryes–
dailyIncrementGbnumberyes–
fullBackupGbnumberyes–
monthlyCopiesintegeryes–
weeklyCopiesintegeryes–

No output schema declared.

No examples provided.

estimate_storage_growth ~49

Project storage size over up to 120 months at a constant monthly growth rate.

NameTypeReqDescription
currentGbnumberyes–
monthlyGrowthPercentnumberyes–
monthsintegeryes–

No output schema declared.

No examples provided.

ip_range_to_cidr ~47

Convert an IPv4 or IPv6 address range into the smallest set of CIDR blocks that covers it exactly.

NameTypeReqDescription
endstringyes–
startstringyes–

No output schema declared.

No examples provided.

looking_glass_path ~52

Sample the route from the DotMoose network in Canada to a public host or IP address, up to 20 hops with three probes per hop.

NameTypeReqDescription
family–––
targetstringyes–

No output schema declared.

No examples provided.

looking_glass_ping ~44

Send four ICMP echo probes from the DotMoose network in Canada to a public host or IP address.

NameTypeReqDescription
family–––
targetstringyes–

No output schema declared.

No examples provided.

looking_glass_traceroute ~54

Trace the route from the DotMoose network in Canada to a public host or IP address, up to 20 hops with one probe per hop.

NameTypeReqDescription
family–––
targetstringyes–

No output schema declared.

No examples provided.

lookup_domain_rdap ~36

Return the public RDAP registration summary for a domain. Registrant contact fields are not returned.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

lookup_ip_info ~41

Resolve a hostname, or take an IP address directly, and return RDAP network data and the ASN for each public address.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

measure_web_performance ~55

Measure DNS, connect, TLS, and time to first byte for a URL from the DotMoose diagnostic node. This is a network timing sample. It is not a browser rendering benchmark.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

test_robots_txt ~51

Fetch the robots.txt for a site and test whether a user agent may fetch a given path.

NameTypeReqDescription
pathstring––
targetstringyes–
userAgentstring––

No output schema declared.

No examples provided.

trace_cname_chain ~36

Follow the CNAME chain for a hostname, up to 12 aliases, and report loops.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

validate_sitemap ~34

Fetch the sitemap for a site and report its structure, URL count, and fetch errors.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.dotmoosehosting/dotmoose-tools MCP server?

io.github.dotmoosehosting/dotmoose-tools is a hosted endpoint at https://mcp.dotmoose.com/tools/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 · mcp.dotmoose.com

# add to Claude Code
claude mcp add --transport http dotmoosehosting-dotmoose-tools 'https://mcp.dotmoose.com/tools/mcp'
Common questions

What is the io.github.dotmoosehosting/dotmoose-tools MCP server?

io.github.dotmoosehosting/dotmoose-tools is an MCP server listed in the public MCP registry as io.github.dotmoosehosting/dotmoose-tools. Public DNS, mail, TLS, and web diagnostics plus Looking Glass probes via remote MCP. This page covers its hosted endpoint (https://mcp.dotmoose.com/tools/mcp).

Is the io.github.dotmoosehosting/dotmoose-tools MCP server safe to use?

io.github.dotmoosehosting/dotmoose-tools scores 60 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 io.github.dotmoosehosting/dotmoose-tools MCP server expose?

io.github.dotmoosehosting/dotmoose-tools exposes 40 tools: check_dns_propagation, check_domain_delegation, check_dnssec, trace_cname_chain, lookup_domain_rdap, and 35 more. Their descriptions and schemas cost roughly 1,758 tokens of context every time the server is loaded.

Does the io.github.dotmoosehosting/dotmoose-tools MCP server require authentication?

No. We connected to io.github.dotmoosehosting/dotmoose-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.dotmoosehosting/dotmoose-tools MCP server still maintained?

io.github.dotmoosehosting/dotmoose-tools is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.