Developer · Remote MCP server
DoDomain
Connect custom domains via AI agents: DNS pre-flight checks, hand-off connect sessions and checks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.dodomain/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-10
- Updated
- 2026-09-10
- Publisher
- io.dodomain
- Namespace
- Namespace verified by the MCP Registry via the domain dodomain.io · how
- Listed under
- Flights MCP servers
- Website
- dodomain.io/docs/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.dodomain.io/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect DoDomain
DoDomain is a remote MCP server: there is nothing to install. Its endpoint is https://app.dodomain.io/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, dodomain.io, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| DocsMintCloud or self-hosted knowledge for AI agents: hybrid search, reranking, GraphRAG, scoped MCP tools. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Doctree MCPBM25 search + tree navigation over markdown docs for AI agents. No embeddings, no LLM calls. | Local · stdio |
| DocuwriterGenerate, search, and manage codebase documentation on DocuWriter.ai. 72 tools incl. Autopilot. | Remote · HTTPLive check: sign-in required |
| DocvetDocstring quality vetting for Python -- enrichment, freshness, coverage, and presence checks. | Local · stdio |
| DojoGenesis MCPPractice library for coding agents: skill search/invoke, seed patches, scout, reflect, ADR writer. | Local · stdio |
| Dokploy MCP ServerDokploy MCP server: manage apps, Docker Compose, databases, domains, backups, and servers. | Local · stdio |
| Domain & Company Intel MCPDomain intel for AI agents: RDAP registration, DNS, email deliverability, tech stack. | Remote · HTTPLive check: ✓ handshake |
| Domain Checker MCPFast domain availability checker. DNS + RDAP/WHOIS verification. | Local · stdio |