
Dotmoose Account
io.github.dotmoosehosting由 GitHub 账号 dotmoosehosting 发布v1.0.0更新于 Oct 30, 2026
Manage existing DotMoose hosting services through OAuth-protected MCP tools.
概览
DotMoose 远程 MCP 端点,让助手浏览主机产品、运行公开的 DNS/TLS/邮件诊断,并通过 OAuth 管理现有客户服务。
- 可以做什么
- 查询产品、报价、推荐与促销,检查域名可用性并规划应用发布
- 运行只读网络诊断:DNS、DNSSEC、RDAP、TLS、HTTP、邮件认证记录、黑名单与 Looking Glass 探测
- 使用本地计算器处理子网、CIDR、带宽、存储增长以及 SPF/DMARC 记录构建
- 查看已认证账户的服务与支持状态,准备部署或上线就绪性变更
- 先准备再按操作 ID 执行需确认的账户操作
- 适用场景
- 适合让助手调研 DotMoose 主机与域名、排查 DNS、TLS、HTTP 或邮件配置问题,或在对话中操作已有的 DotMoose 账户。
- 运行要求
- 远程 Streamable HTTP 端点,无需本地安装。公开端点与工具端点无需认证;账户端点需通过浏览器完成 OAuth 2.1 登录,并按所选工具申请权限范围。诊断目标必须解析为公网地址。
安装
在 SourceWeft 中
- 打开 控制台中的 Dotmoose Account,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.dotmoosehosting%2Fdotmoose-account/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"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.
来源:README.md,提交 8ff4476
工具
0版本历史
1- v1.0.0最新Oct 23, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分