io.github.dotmoosehosting/dotmoose
REMOTE · MCP.DOTMOOSE.COM
Discover DotMoose hosting and domains through a production remote MCP server.
Available components
Last scanned (17 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Cloud Infrastructure
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 855 tokens (~106/item across 8 items; 8 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
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.
- 23 Oct 26 68
First indexed and scored.
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 23 Oct 2026 · Probed https://mcp.dotmoose.com/public/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/public/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.dotmoose.com/public/mcp | HTTPS enforced | 308 | https://mcp.dotmoose.com/public/mcp |
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 →
check_domain_availability Check DotMoose domain availability ~39
Check a normalized domain using the live DotMoose domain lookup path. This never returns WHOIS contact data.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
list_current_promotions List current DotMoose promotions ~66
List only promotion codes explicitly curated for public MCP visibility and still active in current DotMoose commerce data. Product and billing-cycle filters are optional. First-party checkout revalidates final eligibility and stacking.
| Name | Type | Req | Description |
|---|---|---|---|
| billingCycle | string | – | – |
| productRef | string | – | – |
No output schema declared.
No examples provided.
list_public_products List current DotMoose products and other offerings ~89
List fixed products that are currently public, active, available for sale, and orderable according to fresh DotMoose commerce data. When no fixed-family filter is supplied, the response also includes a curated directory for domains, Dedicated quotes, add-ons, licences, migrations, account features, and application-based programs. Those entries are guided handoffs rather than fixed products.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | – |
No output schema declared.
No examples provided.
plan_app_publication Plan how to publish an app or tool on DotMoose ~148
Analyze non-sensitive project characteristics and recommend the smallest current DotMoose product and publication workflow for a website, app, API, bot, MCP server/MCP App, SaaS project, or downloadable tool. This tool is read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| appType | string | – | – |
| backgroundWorkers | boolean | – | – |
| customTcpPorts | boolean | – | – |
| expectedTraffic | string | – | – |
| hasDockerfile | boolean | – | – |
| needsCron | boolean | – | – |
| needsDatabase | boolean | – | – |
| needsWebSockets | boolean | – | – |
| persistentStorageGb | number | – | – |
| requiresRoot | boolean | – | – |
| runtime | string | – | – |
No output schema declared.
No examples provided.
quote_domain Quote a DotMoose domain ~61
Return current standard CAD TLD pricing for registration, transfer, or renewal. Premium-domain pricing is explicitly non-authoritative until first-party checkout recalculates it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| operation | string | – | – |
| years | integer | – | – |
No output schema declared.
No examples provided.
quote_public_product Quote a current DotMoose product ~53
Return a short-lived non-binding CAD quote sourced from current DotMoose sales data. Final tax and payment are completed in first-party checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| billingCycle | string | – | – |
| productRef | string | yes | – |
No output schema declared.
No examples provided.
recommend_product Recommend a current DotMoose product ~107
Recommend the smallest currently orderable public product set for a goal, or return the workload-specific Dedicated quote handoff when bare metal is explicitly requested. Fixed-product recommendations and optional backup/object-storage components come from live public availability, not a hard-coded price table.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedTraffic | string | – | – |
| needsBackup | boolean | – | – |
| needsDomain | boolean | – | – |
| needsObjectStorage | boolean | – | – |
| needsRoot | boolean | – | – |
| workload | string | – | – |
No output schema declared.
No examples provided.
start_signup Start DotMoose signup/checkout ~77
Create a short-lived signed product-selection intent and return a clients.dotmoose.com continuation URL. Account creation, required customer information, and checkout are completed on the first-party continuation page.
| Name | Type | Req | Description |
|---|---|---|---|
| billingCycle | string | – | – |
| domainIntent | object | – | – |
| productRef | string | yes | – |
| promotionCode | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.dotmoosehosting/dotmoose MCP server?
io.github.dotmoosehosting/dotmoose is a hosted endpoint at https://mcp.dotmoose.com/public/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
claude mcp add --transport http dotmoosehosting-dotmoose 'https://mcp.dotmoose.com/public/mcp'
What is the io.github.dotmoosehosting/dotmoose MCP server?
io.github.dotmoosehosting/dotmoose is an MCP server listed in the public MCP registry as io.github.dotmoosehosting/dotmoose. Discover DotMoose hosting and domains through a production remote MCP server. This page covers its hosted endpoint (https://mcp.dotmoose.com/public/mcp).
Is the io.github.dotmoosehosting/dotmoose MCP server safe to use?
io.github.dotmoosehosting/dotmoose scores 68 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 MCP server expose?
io.github.dotmoosehosting/dotmoose exposes 8 tools: list_public_products, recommend_product, list_current_promotions, plan_app_publication, quote_public_product, and 3 more. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Does the io.github.dotmoosehosting/dotmoose MCP server require authentication?
No. We connected to io.github.dotmoosehosting/dotmoose without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.dotmoosehosting/dotmoose MCP server still maintained?
io.github.dotmoosehosting/dotmoose is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.