Dotmoose

io.github.dotmoosehostingPublished by GitHub account dotmoosehostingv1.0.0Updated Oct 27, 2026

Discover DotMoose hosting and domains through a production remote MCP server.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureBusiness & Commerce

Overview

AI-generated overview

Remote DotMoose MCP server for browsing hosting products, promotions and domain pricing, getting quotes, and handing off to first-party signup.

What you can do
  • List and recommend currently orderable public hosting products, including Dedicated quote handoffs and optional backup or object-storage components
  • List active promotion codes and plan a publication workflow for a website, app, API, bot, MCP server or SaaS project
  • Check domain availability and quote standard CAD TLD pricing for registration, transfer or renewal
  • Create a short-lived non-binding CAD quote for a product
  • Start a signed product-selection intent and return a first-party signup continuation link
When to use it
Useful when someone wants an assistant to compare DotMoose hosting plans, check domain availability or pricing, or get a preliminary quote before signing up. It is a discovery and planning layer, not a management tool for an existing account.
Requirements
A remote Streamable HTTP endpoint; no local install or package is needed. The public endpoint used here requires no authentication, account or API key. The README lists separate endpoints for free diagnostics and for OAuth 2.1-protected customer account operations.
Before you install
Quotes are short-lived and non-binding, and premium-domain pricing is non-authoritative until checkout recalculates it. Promotions are revalidated at checkout. Signup and payment happen on the first-party site; the README warns against putting passwords, API tokens, payment details, MFA codes, transfer codes or deployment secrets into MCP configuration or chat prompts.

Installation

In SourceWeft

  1. Open Dotmoose in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.dotmoosehosting%2Fdotmoose/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dotmoose": {
      "type": "http",
      "url": "https://mcp.dotmoose.com/public/mcp"
    }
  }
}

README

DotMoose MCP

Official Model Context Protocol endpoints for DotMoose hosting, domains, support, diagnostics, and managed application deployment.

This repository contains public connection metadata and documentation. The production implementation remains operated by DotMoose so customers do not need to install or run a local server.

Endpoints

EndpointAuthenticationIntended use
https://mcp.dotmoose.com/public/mcpNoneProduct and domain discovery, quotes, publication planning, and a secure first-party signup handoff
https://mcp.dotmoose.com/tools/mcpNonePublic DNS, domain, mail, TLS, HTTP, and website diagnostics, Looking Glass probes from Canada, and network calculators
https://mcp.dotmoose.com/mcpOAuth 2.1Existing-customer account, service, support, diagnostics, and confirmation-gated operations

Health checks:

  • https://mcp.dotmoose.com/public/healthz
  • https://mcp.dotmoose.com/tools/healthz
  • https://mcp.dotmoose.com/healthz

The service uses stateless Streamable HTTP with the MCP 2026-07-28 protocol revision and a 2025-11-25 compatibility path for established clients.

Open any endpoint in a normal web browser to see its tool inventory, setup examples, and safety model. These documentation pages do not require authentication. MCP protocol requests to the account endpoint still require OAuth 2.1; strict content negotiation keeps browser HTML and protocol traffic separate.

Quick connection

For product and domain discovery, add this remote server to an MCP client:

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

For the free diagnostic tools, add the Tools endpoint instead:

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

Existing DotMoose customers can use the authenticated endpoint. Compatible clients open DotMoose authorization in the browser and request the scopes needed for the selected tool:

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

Do not put a DotMoose password, API token, payment detail, MFA code, domain transfer code, or deployment secret in an MCP configuration file or chat prompt.

Client setup

ChatGPT and Codex

The repository includes a portable Agent Plugin manifest. In supported local Codex clients, add this repository as a plugin marketplace source:

text
codex plugin marketplace add dotmoosehosting/dotmoose-mcp

Restart the desktop app, open the Plugins Directory, select the DotMoose source, and install DotMoose. The install includes the public discovery, public diagnostic, and OAuth-protected account endpoints. Authentication opens only when an account-scoped tool needs it.

For direct testing in ChatGPT Developer Mode, add https://mcp.dotmoose.com/mcp as a custom MCP server.

The root plugin is the all-in-one local install. OpenAI's public review flow accepts one MCP server per plugin, so docs/openai-submission.md documents the separately validated account, discovery, and diagnostics submission bundles.

Cursor

Add either endpoint to your user or project mcp.json. Cursor can also install portable Agent Plugins from a public Git repository, so this repository can be submitted directly to the Cursor Marketplace.

Claude, VS Code, and other MCP clients

Use the remote Streamable HTTP URL in the client's MCP server settings. Choose the public endpoint for anonymous discovery or the account endpoint for OAuth-protected customer operations.

What the tools do

The anonymous endpoint exposes eight intentionally narrow tools:

  • list_public_products
  • quote_public_product
  • recommend_product
  • list_current_promotions
  • check_domain_availability
  • quote_domain
  • plan_app_publication
  • start_signup

The Tools endpoint exposes 40 read-only tools that need no account:

  • 33 diagnostics that run the same public checks as the free tools at dotmoose.com/tools: DNS propagation, delegation, DNSSEC, CNAME chains, RDAP, IP and reverse DNS lookups, TLS certificate and configuration, HTTP chains and status, web timing, website security, security.txt, compression, IPv6, favicon, link audits, page metadata, robots.txt, sitemaps, SPF, DMARC, DKIM, MX, SMTP STARTTLS, MTA-STS, TLS-RPT, BIMI, blacklist checks, and Looking Glass ping, traceroute, and path probes from the DotMoose network in Canada.
  • 7 local calculators and builders: subnet calculation, IP range to CIDR conversion, bandwidth calculation, storage growth and backup retention estimates, and SPF and DMARC record builders.

Targets must resolve only to public addresses. The diagnostic service rejects private, loopback, link-local, and reserved destinations. Results are point-in-time observations and each one links to the matching tool page on dotmoose.com.

The account endpoint exposes tools for session and service discovery, support, diagnostics, security assessment, deployment planning, source and image deployment preparation, launch-readiness verification, and other account operations. See docs/tools.md for the supported workflows and safeguards.

Safe action model

DotMoose separates planning from execution:

  1. Read tools inspect the authenticated account and service state.
  2. Prepare tools validate the requested change and store a short-lived action intent.
  3. The client shows the action, consequences, and required confirmation.
  4. Execute tools accept only the prepared action ID. They cannot replace its target or payload.
  5. The service rechecks OAuth scopes, service version, capacity, billing state, and provider preconditions before mutation.

Managed App deployment accepts either an immutable OCI image digest or an exact GitHub HTTPS repository and safe build settings. Secrets remain saved references in DotMoose and are never accepted as tool input.

Commercial boundary

The public MCP can create a short-lived selection intent and send the user to clients.dotmoose.com for first-party signup and checkout. It does not collect personal, password, MFA, payment, or credential data.

Managed App purchasing and general availability are controlled separately from the MCP software release. A working MCP deployment path does not by itself promise that a product is available for new purchase.

Support and policies

License

The distribution metadata and documentation in this repository are licensed under the MIT License. DotMoose service use remains governed by the linked service terms.

Source: README.md at commit 8ff4476

Tools

8

list_public_products

List current DotMoose products and other offerings

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.

Parametersfamily

recommend_product

Recommend a current DotMoose product

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.

ParametersworkloadneedsRootneedsBackupneedsDomainexpectedTrafficneedsObjectStorage

list_current_promotions

List current DotMoose promotions

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.

ParametersproductRefbillingCycle

plan_app_publication

Plan how to publish an app or tool on DotMoose

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.

ParametersappTyperuntimeneedsCronrequiresRoothasDockerfileneedsDatabasecustomTcpPortsexpectedTrafficneedsWebSocketsbackgroundWorkerspersistentStorageGb

quote_public_product

Quote a current DotMoose product

Return a short-lived non-binding CAD quote sourced from current DotMoose sales data. Final tax and payment are completed in first-party checkout.

ParametersproductRefrequiredbillingCycle

check_domain_availability

Check DotMoose domain availability

Check a normalized domain using the live DotMoose domain lookup path. This never returns WHOIS contact data.

Parametersdomainrequired

quote_domain

Quote a DotMoose domain

Return current standard CAD TLD pricing for registration, transfer, or renewal. Premium-domain pricing is explicitly non-authoritative until first-party checkout recalculates it.

Parametersyearsdomainrequiredoperation

start_signup

Start DotMoose signup/checkout

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.

ParametersproductRefrequiredbillingCycledomainIntentpromotionCode

Version history

1
  1. v1.0.0LatestOct 23, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts