# MCPDomain (remote · mcpdomain.ai)

Buy & manage domains from any AI chat: availability, register, DNS, email forwarding, AI bot stats.

- Trust score: 61/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcpdomain.ai`: 61/100 (this document), [markdown](https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain.md), [page](https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain)
- npm · `mcpdomain`: 39/100, [markdown](https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain-2.md), [page](https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain-2)

## Channel facts

- Endpoint: `https://mcpdomain.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.7`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 962 tokens (~106/item across 9 items; 7 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http danboabes-mcpdomain https://mcpdomain.ai/mcp
```

### Codex

```toml
[mcp_servers.danboabes-mcpdomain]
url = "https://mcpdomain.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danboabes-mcpdomain": {
      "type": "remote",
      "url": "https://mcpdomain.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add danboabes-mcpdomain --url https://mcpdomain.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  danboabes-mcpdomain:
    url: "https://mcpdomain.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "danboabes-mcpdomain": {
      "type": "http",
      "url": "https://mcpdomain.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 60, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (7)

### `check_domain_availability` (~84 tokens)

Check whether a specific internet domain name is available for registration. Returns availability status, price, and alternatives if taken. WHEN TO USE: user asks 'is X.com available?' or 'can I register Y.io?'. ALWAYS call this before register_new_domain.

Input parameters:

- `domain` (string, required): Complete domain name with TLD, e.g. 'sweetcrumbs.com'

### `suggest_available_domains` (~110 tokens)

Generate creative domain name suggestions from keywords or business description, with real-time availability checks. WHEN TO USE: user says 'help me find a domain for my bakery' or 'what domain should I use for X?'.

Input parameters:

- `keywords` (string, required): Business name or description, e.g. 'sweet crumbs bakery'
- `max_results` (number): Max suggestions. Default: 8
- `tlds` (array): TLDs to search. Default: ['.com','.co','.io']

### `register_new_domain` (~159 tokens)

Register a new domain. Returns a Stripe checkout URL for payment. After payment, domain is registered with FREE email forwarding, DNS, and AI bot monitoring. ALWAYS call check_domain_availability first. Collect first_name, last_name, email from user before calling.

Input parameters:

- `domain` (string, required): Full domain name to register, e.g. 'sweetcrumbs.com'. Must first be verified free via check_domain_availability.
- `registrant` (object, required): Legal registrant for the domain. Appears in WHOIS (private by default where the TLD supports it) and receives ICANN verification and renewal emails.
- `years` (number): Registration period in years. Default: 1. Most TLDs allow 1-10 years.

### `configure_domain_email` (~143 tokens)

Set up email forwarding for a registered domain. Forward any@domain to Gmail/Outlook. No MX records needed. WHEN TO USE: user just registered a domain, or asks about professional email.

Input parameters:

- `aliases` (array): Specific forwarding rules instead of a catch-all. Each rule routes one address @domain to one destination inbox.
- `catch_all_to` (string): Forward ALL emails sent to any address @domain to this inbox (e.g. 'you@gmail.com'). Mutually exclusive with 'aliases' — use one or the other.
- `domain` (string, required): A domain previously registered via register_new_domain, e.g. 'sweetcrumbs.com'.

### `configure_domain_dns` (~95 tokens)

Add/update DNS records (A, CNAME, MX, TXT). Use to point domain to Vercel, Netlify, GitHub Pages etc. WHEN TO USE: user wants to connect domain to hosting.

Input parameters:

- `domain` (string, required): A domain previously registered via register_new_domain.
- `records` (array, required): One or more DNS records to add or update. Existing records with the same type+name combination are replaced.

### `get_my_domain_details` (~98 tokens)

Look up the registration status of a domain you previously registered through MCPDomain. Returns: registered_at, expires_at, current nameservers, and email-forwarding status (active / pending verification / pending NS propagation / etc). WHEN TO USE: user asks 'is my domain ready?', 'what's the status of X?', 'did email forwarding finish setting up?'.

Input parameters:

- `domain` (string, required): A domain previously registered via register_new_domain

### `transfer_existing_domain` (~128 tokens)

Transfer a domain from another registrar (GoDaddy, Namecheap etc) to MCPDomain. Requires EPP/auth code. Transfer takes 5-7 days and adds 1 year to expiry.

Input parameters:

- `auth_code` (string, required): EPP / authorization code from the current registrar. Also called 'transfer secret', 'auth info', or 'domain secret' in some registrar UIs.
- `domain` (string, required): Domain to transfer in, e.g. 'example.com'. Must be at least 60 days old since registration or a previous transfer, and must be unlocked at the losing registrar.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 61
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcpdomain.ai/mcp
- Repository: https://github.com/danboabes/mcpdomain
- Website: https://mcpdomain.ai/
- Changelog RSS feed: https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain/changelog.json
- HTML version of this page: https://verifymcp.io/servers/danboabes-mcpdomain/mcpdomain