# io.github.dotmoosehosting/dotmoose-tools (remote · mcp.dotmoose.com)

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

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `mcp.dotmoose.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/dotmoosehosting-dotmoose-tools/tools-mcp.md), [page](https://verifymcp.io/servers/dotmoosehosting-dotmoose-tools/tools-mcp)

## Channel facts

- Endpoint: `https://mcp.dotmoose.com/tools/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-10-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1910 tokens (~47/item across 40 items; 40 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 41 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).

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

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

### Claude

```bash
claude mcp add --transport http dotmoosehosting-dotmoose-tools 'https://mcp.dotmoose.com/tools/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dotmoosehosting-dotmoose-tools": {
      "url": "https://mcp.dotmoose.com/tools/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dotmoosehosting-dotmoose-tools": {
      "type": "http",
      "url": "https://mcp.dotmoose.com/tools/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dotmoosehosting-dotmoose-tools]
url = "https://mcp.dotmoose.com/tools/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dotmoosehosting-dotmoose-tools": {
      "type": "remote",
      "url": "https://mcp.dotmoose.com/tools/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dotmoosehosting-dotmoose-tools --url 'https://mcp.dotmoose.com/tools/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dotmoosehosting-dotmoose-tools:
    url: "https://mcp.dotmoose.com/tools/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dotmoosehosting-dotmoose-tools": {
      "Transport": "http",
      "Url": "https://mcp.dotmoose.com/tools/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dotmoosehosting-dotmoose-tools -t streamable-http -u 'https://mcp.dotmoose.com/tools/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dotmoosehosting-dotmoose-tools": {
      "type": "http",
      "url": "https://mcp.dotmoose.com/tools/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-10-24 (score 60)

First indexed and scored.

## MCP tools (40)

### `check_dns_propagation` (~47 tokens)

Check DNS propagation

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

Input parameters:

- `domain` (string, required)

### `check_domain_delegation` (~38 tokens)

Check domain delegation

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

Input parameters:

- `domain` (string, required)

### `check_dnssec` (~39 tokens)

Check DNSSEC

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

Input parameters:

- `domain` (string, required)

### `trace_cname_chain` (~36 tokens)

Trace a CNAME chain

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

Input parameters:

- `domain` (string, required)

### `lookup_domain_rdap` (~36 tokens)

Look up domain registration (RDAP)

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

Input parameters:

- `domain` (string, required)

### `lookup_ip_info` (~41 tokens)

Look up IP information

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

Input parameters:

- `target` (string, required)

### `check_forward_confirmed_rdns` (~40 tokens)

Check forward-confirmed reverse DNS

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

Input parameters:

- `ip` (string, required)

### `check_tls_certificate` (~42 tokens)

Check a TLS certificate

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

Input parameters:

- `target` (string, required)

### `check_tls_configuration` (~30 tokens)

Check TLS configuration

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

Input parameters:

- `target` (string, required)

### `check_http_chain` (~31 tokens)

Check an HTTP redirect chain

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

Input parameters:

- `target` (string, required)

### `check_http_status` (~28 tokens)

Check HTTP status

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

Input parameters:

- `target` (string, required)

### `measure_web_performance` (~55 tokens)

Measure web timing

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.

Input parameters:

- `target` (string, required)

### `check_website_security` (~41 tokens)

Check website security controls

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

Input parameters:

- `target` (string, required)

### `check_security_txt` (~27 tokens)

Check security.txt

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

Input parameters:

- `target` (string, required)

### `check_compression` (~37 tokens)

Check compression

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

Input parameters:

- `target` (string, required)

### `check_ipv6_website` (~34 tokens)

Check IPv6 website reachability

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

Input parameters:

- `target` (string, required)

### `check_favicon` (~32 tokens)

Check a favicon

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

Input parameters:

- `target` (string, required)

### `audit_page_links` (~47 tokens)

Audit links on one page

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.

Input parameters:

- `target` (string, required)

### `check_page_metadata` (~43 tokens)

Check page metadata

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

Input parameters:

- `target` (string, required)

### `test_robots_txt` (~51 tokens)

Test robots.txt rules

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

Input parameters:

- `path` (string)
- `target` (string, required)
- `userAgent` (string)

### `validate_sitemap` (~34 tokens)

Validate a sitemap

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

Input parameters:

- `target` (string, required)

### `check_spf` (~41 tokens)

Check an SPF record

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

Input parameters:

- `domain` (string, required)

### `check_dmarc` (~32 tokens)

Check a DMARC record

Read the DMARC record published at _dmarc for a domain.

Input parameters:

- `domain` (string, required)

### `check_dkim` (~36 tokens)

Check a DKIM record

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

Input parameters:

- `domain` (string, required)
- `selector` (string, required)

### `check_mx_records` (~36 tokens)

Check MX records

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

Input parameters:

- `domain` (string, required)

### `check_smtp_starttls` (~54 tokens)

Check SMTP STARTTLS

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.

Input parameters:

- `domain` (string, required)

### `check_mta_sts` (~35 tokens)

Check MTA-STS

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

Input parameters:

- `domain` (string, required)

### `check_tls_rpt` (~33 tokens)

Check TLS-RPT

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

Input parameters:

- `domain` (string, required)

### `check_bimi` (~40 tokens)

Check a BIMI record

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

Input parameters:

- `domain` (string, required)
- `selector` (string)

### `check_ip_blacklists` (~38 tokens)

Check IP blacklists

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

Input parameters:

- `target` (string, required)

### `looking_glass_ping` (~44 tokens)

Looking Glass ping

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

Input parameters:

- `family`
- `target` (string, required)

### `looking_glass_traceroute` (~54 tokens)

Looking Glass traceroute

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.

Input parameters:

- `family`
- `target` (string, required)

### `looking_glass_path` (~52 tokens)

Looking Glass path sample

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.

Input parameters:

- `family`
- `target` (string, required)

### `calculate_subnet` (~41 tokens)

Subnet calculator

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

Input parameters:

- `cidr` (string, required)

### `ip_range_to_cidr` (~47 tokens)

IP range to CIDR

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

Input parameters:

- `end` (string, required)
- `start` (string, required)

### `calculate_bandwidth` (~67 tokens)

Bandwidth calculator

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.

Input parameters:

- `fileSizeGb` (number)
- `linkMbps` (number)
- `monthlyTransferGb` (number)

### `estimate_storage_growth` (~49 tokens)

Storage growth estimator

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

Input parameters:

- `currentGb` (number, required)
- `monthlyGrowthPercent` (number, required)
- `months` (integer, required)

### `estimate_backup_retention` (~77 tokens)

Backup retention estimator

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

Input parameters:

- `dailyCopies` (integer, required)
- `dailyIncrementGb` (number, required)
- `fullBackupGb` (number, required)
- `monthlyCopies` (integer, required)
- `weeklyCopies` (integer, required)

### `build_spf_record` (~95 tokens)

SPF record builder

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.

Input parameters:

- `allQualifier` (string)
- `includes` (array)
- `ipv4` (array)
- `ipv6` (array)
- `redirectDomain` (string)
- `useA` (boolean)
- `useMx` (boolean)

### `build_dmarc_record` (~78 tokens)

DMARC record builder

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

Input parameters:

- `failureReporting` (string)
- `percent` (integer)
- `policy` (string, required)
- `rua` (array)
- `ruf` (array)
- `subdomainPolicy` (string)

## Diagnostics

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

## Score history

- 2026-10-24: 60

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

## Links

- Remote endpoint: https://mcp.dotmoose.com/tools/mcp
- Repository: https://github.com/dotmoosehosting/dotmoose-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dotmoosehosting-dotmoose-tools/tools-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dotmoosehosting-dotmoose-tools/tools-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dotmoosehosting-dotmoose-tools/tools-mcp