Dotmoose Account MCP server
online · 100% uptimeManage existing DotMoose hosting services through OAuth-protected MCP tools.
1 stars
Reviews
Write oneNobody has reviewed Dotmoose Account yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Dotmoose Account tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 331ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Dotmoose Account compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 95/100
- higher than 97% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 202 ms
- faster than 63% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Install Dotmoose Account in Claude Code, Cursor or VS Code
claude mcp add --transport http dotmoose-account https://mcp.dotmoose.com/mcp
What the publisher says
From the Dotmoose Account repository's README, as published. We do not edit it. Read it on GitHub
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/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:
{
"mcpServers": {
"dotmoose-public": {
"url": "https://mcp.dotmoose.com/public/mcp"
}
}
}For the free diagnostic tools, add the Tools endpoint instead:
{
"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:
{
"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:
codex plugin marketplace add dotmoosehosting/dotmoose-mcpRestart 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:
- listpublicproducts
- quotepublicproduct
- recommend_product
- listcurrentpromotions
- checkdomainavailability
- quote_domain
- planapppublication
- start_signup
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Dotmoose Account: common questions
- Is Dotmoose Account MCP server safe?
- Yes, by our scan: it is graded A (95/100). Read the Dotmoose Account safety report
- How do I install Dotmoose Account?
- It runs remotely at mcp.dotmoose.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Dotmoose Account need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Dotmoose Account maintained?
- The last commit was 11 days ago (2026-10-24). The latest release is v1.0.0.
- Is Dotmoose Account up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Dotmoose Account compare with other MCP servers?
- safety score 95/100 (higher than 97% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 202 ms (faster than 63% of 30,031 servers). Full comparison.