MCP servers › io.github.dotmoosehosting › dotmoose-tools

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.github.dotmoosehosting/dotmoose-tools

Public DNS, mail, TLS, and web diagnostics plus Looking Glass probes via remote MCP. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.0.0PowerShellstreamable HTTP40 tools

Summary

io.github.dotmoosehosting/dotmoose-tools is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 40 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 40
Last tested: 2026-10-24

Add to your client

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-24
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version: 2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-24
Package and repository: checked 2026-10-24
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.0.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

40tools

0resources

0prompts

None of its 40 tools are described as changing anything. For 40 the reading was uncertain, so no mark is shown.

check_dns_propagationon 2 other servers
“Check A, AAAA, MX, NS, and TXT answers for a hostname at the Cloudflare, Google, and Quad9 resolvers.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_domain_delegation
“List the delegation nameservers for a domain and the A and AAAA glue addresses for each one.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_dnssecon 1 other server
“Check the DS and DNSKEY records for a domain and whether a validating resolver sets the AD flag on its answers.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
trace_cname_chain
“Follow the CNAME chain for a hostname, up to 12 aliases, and report loops.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
lookup_domain_rdap
“Return the public RDAP registration summary for a domain.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
lookup_ip_info
“Resolve a hostname, or take an IP address directly, and return RDAP network data and the ASN for each public address.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_forward_confirmed_rdns
“Check the PTR record for an IP address and whether the name it returns resolves back to the same address.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- ipstringrequired
check_tls_certificate
“Connect to a host on port 443 and return the TLS version, cipher, and certificate details including expiry and subject alternative names.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_tls_configuration
“Observe which TLS protocol versions a host accepts and summarize its TLS configuration.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_http_chain
“Fetch a URL and return each redirect hop with status codes and response headers.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_http_status
“Fetch a URL and return the final status after following redirects.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
measure_web_performance
“Measure DNS, connect, TLS, and time to first byte for a URL from the DotMoose diagnostic node.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired

Show 28 more tools

check_website_security
“Review the security controls a site exposes in its public responses, including security headers, cookie attributes, and CORS policy.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_security_txt
“Fetch and parse the security.txt file for a site.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_compression
“Check whether a URL is served with gzip or Brotli compression and report the sizes with and without compression.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_ipv6_website
“Check whether a site answers over IPv6 and compare the result with IPv4.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_faviconon 2 other servers
“Locate the favicon a site declares and report its URL, type, and size.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
audit_page_links
“Check up to 20 same-origin links found on one page and report the status of each.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_page_metadata
“Return the title, meta description, canonical URL, headings, hreflang entries, and JSON-LD types found on a page.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
test_robots_txton 1 other server
“Fetch the robots.txt for a site and test whether a user agent may fetch a given path.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- targetstringrequired
- pathstring
- userAgentstring
validate_sitemapon 1 other server
“Fetch the sitemap for a site and report its structure, URL count, and fetch errors.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
check_spfon 6 other servers
“Read the SPF record for a domain and count the DNS lookup terms in the full include chain against the limit of 10.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_dmarcon 7 other servers
“Read the DMARC record published at _dmarc for a domain.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_dkimon 4 other servers
“Read the DKIM public key record for a domain and selector.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
- domainstringrequired
- selectorstringrequired
check_mx_records
“List the MX records for a domain with the A and AAAA addresses of each mail server.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_smtp_starttls
“Connect to the mail servers for a domain on port 25 and report the banner, EHLO response, and STARTTLS support.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_mta_stson 4 other servers
“Read the MTA-STS DNS record and the published policy file for a domain.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_tls_rpt
“Read the TLS-RPT record published at _smtp._tls for a domain.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- domainstringrequired
check_bimion 5 other servers
“Read the BIMI record for a domain and selector.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- domainstringrequired
- selectorstring
check_ip_blacklists
“Check an IP address, or the public addresses a hostname resolves to, against the reviewed DNS blacklist providers.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- targetstringrequired
looking_glass_ping
“Send four ICMP echo probes from the DotMoose network in Canada to a public host or IP address.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- targetstringrequired
- familynumber
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.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- targetstringrequired
- familynumber
looking_glass_path
“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.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- targetstringrequired
- familynumber
calculate_subneton 3 other servers
“Compute the network address, broadcast or last address, and address counts for an IPv4 or IPv6 CIDR block.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- cidrstringrequired
ip_range_to_cidr
“Convert an IPv4 or IPv6 address range into the smallest set of CIDR blocks that covers it exactly.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 2 required
- startstringrequired
- endstringrequired
calculate_bandwidth
“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.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- linkMbpsnumber
- monthlyTransferGbnumber
- fileSizeGbnumber
estimate_storage_growth
“Project storage size over up to 120 months at a constant monthly growth rate.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 3 required
- currentGbnumberrequired
- monthlyGrowthPercentnumberrequired
- monthsintegerrequired
estimate_backup_retention
“Estimate backup storage for a grandfather-father-son retention plan where weekly and monthly copies are full backups and daily copies are increments.”
Publisher declares: read-only yes · destructive no · open-world no
5 inputs, 5 required
- fullBackupGbnumberrequired
- dailyIncrementGbnumberrequired
- dailyCopiesintegerrequired
- weeklyCopiesintegerrequired
- monthlyCopiesintegerrequired
build_spf_record
“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.”
Publisher declares: read-only yes · destructive no · open-world no
7 inputs
- ipv4array
- ipv6array
- includesarray
- useAboolean
- useMxboolean
- redirectDomainstring
- allQualifierstring
build_dmarc_record
“Assemble a DMARC record from a policy, optional subdomain policy, report addresses, and enforcement percentage.”
Publisher declares: read-only yes · destructive no · open-world no
6 inputs, 1 required
- policystringrequired
- subdomainPolicystring
- ruaarray
- rufarray
- percentinteger
- failureReportingstring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 0% of 67
Tools with a description: 100% of 40
Typical description length: 101 characters

The tool set

Counted from the listing

Tools: 40
Size of the list: about 5,259 tokens for an agent to load (characters ÷ 4)
Naming: 40 of 40 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 40 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.dotmoose.com/tools/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.dotmoose.com/tools/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.dotmoose.com/tools/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/dotmoosehosting/dotmoose-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.dotmoosehosting · 3 servers
GitHub owner: an organization (dotmoosehosting)

Repository: github.com/dotmoosehosting/dotmoose-mcp
Stars: 1
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.dotmoosehosting/dotmoose-tools

Answered from the data above

Is io.github.dotmoosehosting/dotmoose-tools safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.dotmoosehosting/dotmoose-tools need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.dotmoosehosting/dotmoose-tools been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Where is the source code of io.github.dotmoosehosting/dotmoose-tools?

In github.com/dotmoosehosting/dotmoose-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
588 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 40 tools, 0 resources, 0 prompts.
3,752 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

PowerShell

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.dotmoosehosting/dotmoose-tools: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.github.dotmoosehosting/dotmoose-tools

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.dotmoosehosting/dotmoose-tools)](https://protocolprobe.com/mcp/servers/io.github.dotmoosehosting/dotmoose-tools)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology