
Dotmoose Account
io.github.dotmoosehostingPublished by GitHub account dotmoosehostingv1.0.0Updated Oct 30, 2026
Manage existing DotMoose hosting services through OAuth-protected MCP tools.
Overview
Remote DotMoose MCP endpoint that lets an assistant browse hosting products, run public DNS/TLS/mail diagnostics, and manage existing customer services via…
- What you can do
- Discover products, get quotes, recommendations, promotions, check domain availability and plan app publication
- Run read-only network diagnostics: DNS, DNSSEC, RDAP, TLS, HTTP, email authentication records, blacklists and Looking Glass probes
- Use local calculators for subnets, CIDR, bandwidth, storage growth and SPF/DMARC record building
- Inspect an authenticated account's services and support state, and prepare deployment or launch-readiness changes
- Prepare and then execute confirmation-gated account actions by action ID
- When to use it
- Useful when you want an assistant to research DotMoose hosting and domains, troubleshoot DNS, TLS, HTTP or email configuration, or operate an existing DotMoose account without leaving the chat.
- Requirements
- A remote Streamable HTTP endpoint; no local install. The public and tools endpoints need no authentication. The account endpoint requires OAuth 2.1 sign-in through a browser, with scopes requested per tool. Diagnostic targets must resolve to public addresses only.
Installation
In SourceWeft
- Open Dotmoose Account in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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-account/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"dotmoose-account": {
"type": "http",
"url": "https://mcp.dotmoose.com/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
Health checks:
https://mcp.dotmoose.com/public/healthzhttps://mcp.dotmoose.com/tools/healthzhttps://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:
For the free diagnostic tools, add the Tools endpoint instead:
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:
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:
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_productsquote_public_productrecommend_productlist_current_promotionscheck_domain_availabilityquote_domainplan_app_publicationstart_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:
- Read tools inspect the authenticated account and service state.
- Prepare tools validate the requested change and store a short-lived action intent.
- The client shows the action, consequences, and required confirmation.
- Execute tools accept only the prepared action ID. They cannot replace its target or payload.
- 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
- Website: https://dotmoose.com/
- Support: https://dotmoose.com/support/
- Privacy: https://dotmoose.com/privacy/
- Terms: https://dotmoose.com/terms/
- Security reporting: SECURITY.md
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
0Version history
1- v1.0.0LatestOct 23, 2026
Score
85% 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 listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts