mcpbeat Sign in

DoDomain MCP Server

answering

DoDomain is answering right now. Last checked 10 min ago.

Connect custom domains via AI agents: DNS pre-flight checks, hand-off connect sessions and checks.

Uptime history 54 days of history · worst day 92%
54 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
500 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

DoDomain missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add mcp --transport http https://app.dodomain.io/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.dodomain.io/api/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://app.dodomain.io/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://app.dodomain.io/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://app.dodomain.io/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.dodomain.io/api/mcp streamable-http sign-in 467 ms 10 min ago

Alternatives to DoDomain

same job, measured the same way
CustomDomain™
by customdomain

Custom domains for SaaS and AI agents: search, buy, connect DNS, verify ownership and issue HTTPS.

answering
Domainee
by domainee

Custom domains API for SaaS: connect, verify, and manage customer domains, SSL, and DNS

18 tools answering
Readnpick
by readnpick

EU261/EC261 flight compensation eligibility and flight distance checks via AI agents.

5 tools answering
Opensanctions MCP
by scka-de

Sanctions screening and PEP checks via OpenSanctions API for AI agents

31 installs/wk local only
T
Think MCP
by agentutil

Intent security pre-flight checks for autonomous AI agents.

45 installs/wk local only
Nocompensation
by nocompensation

Flight compensation claims info and submission via AI agents

5 tools answering
HVTracker MCP
by yugantm

Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.

124 installs/wk 8 tools answering
Midnight Rgb
by midnight-rgb

Domain registrar for AI agents. Search, register, and manage domains via API.

40 installs/wk local only

DoDomain — questions

Answers built from our own checks of this server.

Why is there no tool list for DoDomain?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is DoDomain working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 500 ms. The bar chart above shows every period we have measured.
How do I connect DoDomain?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to DoDomain?
No API key is involved. DoDomain answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is DoDomain?
It answers our handshake in 500 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.