Home / MCP registry index / io.github.dotmoosehosting/dotmoose-tools

Dotmoose Tools

io.github.dotmoosehosting/dotmoose-tools in the official MCP registry. Endpoint https://mcp.dotmoose.com/tools/mcp. Source: github.com/dotmoosehosting/dotmoose-mcp.

The registry describes it as: Public DNS, mail, TLS, and web diagnostics plus Looking Glass probes via remote MCP.

We read its 40 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http dotmoose-tools https://mcp.dotmoose.com/tools/mcp

Cursor: ~/.cursor/mcp.json

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

VS Code

code --add-mcp '{"name":"dotmoose-tools","type":"http","url":"https://mcp.dotmoose.com/tools/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

check_dns_propagation check_domain_delegation check_dnssec trace_cname_chain lookup_domain_rdap lookup_ip_info check_forward_confirmed_rdns check_tls_certificate check_tls_configuration check_http_chain check_http_status measure_web_performance check_website_security check_security_txt check_compression check_ipv6_website check_favicon audit_page_links check_page_metadata test_robots_txt validate_sitemap check_spf check_dmarc check_dkim check_mx_records check_smtp_starttls check_mta_sts check_tls_rpt check_bimi check_ip_blacklists looking_glass_ping looking_glass_traceroute looking_glass_path calculate_subnet ip_range_to_cidr calculate_bandwidth estimate_storage_growth estimate_backup_retention build_spf_record build_dmarc_record

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): c2849651f87975fe. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-dotmoosehosting-dotmoose-tools/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-dotmoosehosting-dotmoose-tools)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.