Just Domain
REMOTE · MCP.JUSTDOMAIN.AI · SCANNED SEP 22
Search domain availability and pricing, and check if a domain can transfer in, from chat.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1373 tokens (~343/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_domain_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the Just Domain MCP server?
Just Domain is a hosted endpoint at https://mcp.justdomain.ai/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.justdomain.ai
claude mcp add --transport http ai-justdomain-just-domain 'https://mcp.justdomain.ai/'
{
"mcpServers": {
"ai-justdomain-just-domain": {
"url": "https://mcp.justdomain.ai/"
}
}
} {
"servers": {
"ai-justdomain-just-domain": {
"type": "http",
"url": "https://mcp.justdomain.ai/"
}
}
} [mcp_servers.ai-justdomain-just-domain] url = "https://mcp.justdomain.ai/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-justdomain-just-domain": {
"type": "remote",
"url": "https://mcp.justdomain.ai/",
"enabled": true
}
}
} openclaw mcp add ai-justdomain-just-domain --url 'https://mcp.justdomain.ai/' --transport streamable-http
mcp_servers:
ai-justdomain-just-domain:
url: "https://mcp.justdomain.ai/" {
"McpServers": {
"ai-justdomain-just-domain": {
"Transport": "http",
"Url": "https://mcp.justdomain.ai/"
}
}
} assistant mcp add ai-justdomain-just-domain -t streamable-http -u 'https://mcp.justdomain.ai/'
{
"mcpServers": {
"ai-justdomain-just-domain": {
"type": "http",
"url": "https://mcp.justdomain.ai/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 201 → 343 ▼ functional
- Schema quality: 67% → 75% ▲ functional
- Destructive annotations: pass → 0 functional
- New prompt “jd-transfer-check” functional
- Server version: 0.4.1 → 0.5.1 functional
- New tool “check_domain_transfer” functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 19 Aug 26 0
- Server version: 0.4.0 → 0.4.1 functional
- 13 Aug 26 0
- Resource “Domain search results widget” now points somewhere else: ui://just-domain/search-results-v3.html → ui://just-domain/search-results-v4.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_domains” rewrote its description, which is the text the model reads security
- Schema quality: 147 → 201 ▼ functional
- Schema quality: 75% → 67% ▼ functional
- Prompt “jd-transfer-help” was removed ▼ functional
- Schema quality: good → excellent functional
- Server version: 0.3.6 → 0.4.0 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Resource “Domain search results widget” now points somewhere else: ui://just-domain/search-results-v2.html → ui://just-domain/search-results-v3.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_domains” rewrote its description, which is the text the model reads security
- Schema quality: 133 → 147 ▼ functional
- The server no longer declares the “experimental” capability functional
- Server version: 0.3.5 → 0.3.6 functional
- 4 Aug 26 0
- Tool “search_domains” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.3.4 → 0.3.5 functional
- “search_domains” added an optional parameter “query” cosmetic
- “search_domains” reworded the description of “domains” cosmetic
- “search_domains” made “domains” optional cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://mcp.justdomain.ai/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.justdomain.ai | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 56287035da7af7f1cfa18a9d13b328d33fc |
| SANs: mcp.justdomain.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.justdomain.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| justdomain.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.justdomain.ai/ | Verified | 200 | |
| http (plaintext) | http://mcp.justdomain.ai/ | HTTPS enforced | 301 | https://mcp.justdomain.ai/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domain_transfer Check whether a domain can transfer to Just Domain ~566
Read-only transfer precheck for ONE domain the user already owns at another registrar: could it move to Just Domain, what is stopping it, what would it cost, and does its DNS survive the move. Nothing is ordered, charged, unlocked, or changed. The answer is built from two public sources only, the registry's own RDAP record and our registrar's price list, so it is safe to call without authentication and it reads nothing about the user's account. Read `blockers` before you say anything: an EMPTY list is the only thing that means the domain is ready to move. Every entry carries a plain `detail` sentence you can show as-is, and a `code` you do not recognise must still be reported through its `detail` rather than dropped. `source.rdap: false` means the registry did not answer, so nothing about the domain was established: say that, and never call it ready. `price` is the TOTAL for one full transfer term, not a per-year rate. A .ai transfer adds and charges TWO years because its registry works in two-year units. Do not divide or multiply the amount by a number of years, and do not label it per year; quote `term_note` beside it. `expected_new_expiry` is a projection (the registry's current expiry plus the term), not a date any registry has confirmed, so present it as expected. Moving a domain IN is not a self-service function yet. This tool tells the user whether the domain is eligible to move and what one full term would cost; the move itself is arranged by a person, starting at `transfer_url` and routed through support@just-done.ai. Do not promise what that page will do, and do not describe a payment step for it. Moving a domain OUT of Just Domain IS self-service, and that means a human owner signed in on justdomain.ai in a browser, switching the transfer lock off and issuing the code from their own account. It does not mean you can do it. This tool never returns, accepts, or hints at an authorization (EPP) code, and there is no agent path to unlocking a domain or to hav…
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | One fully-qualified domain the user already owns somewhere else, including its TLD (e.g. 'acme.com'). Not a bare label and not a list: this reads a third-party registry per call. |
| Name | Type | Req | Description |
|---|---|---|---|
| auth_code_policy | string | yes | Constant. The rule about authorization (EPP) codes, restated in the payload so it travels with the answer. Follow it. |
| blockers | array | – | What stands between this domain and a transfer, most blocking first. An EMPTY list is the only thing that means ready. |
| checked_at | string | yes | ISO-8601 instant these facts were read. |
| dns_continuity | object | yes | Does the domain's DNS keep working after the move? A transfer moves sponsorship, not DNS, so the current delegation decides whether the site and the mail survive it. |
| domain | string | yes | – |
| nameservers | array | – | – |
| next_step | string | yes | One sentence you can say to the user about what happens next, already matched to this domain's state. |
| price | – | – | Null when the registrar's price list could not be read. Never estimate a domain transfer price yourself. |
| ready | boolean | yes | TRUE only when `blockers` is empty. It is a convenience over that list and can never disagree with it: anything we could not establish becomes a blocker, so a registry timeout reads as not ready rath… |
| registrar | object | yes | Who sponsors the domain today, as the REGISTRY reports it. |
| source | object | yes | Which public sources actually answered on this request. |
| supported | boolean | yes | Whether Just Domain can accept this ENDING at all. Says nothing about this particular domain - read `blockers` for that. |
| tld | string | yes | – |
| transfer_url | string | yes | The page on justdomain.ai a PERSON opens in a browser to take this further. The handoff out of the chat. |
No examples provided.
search_domains Search domain availability ~343
Read-only availability and pricing lookup for domain names. No purchase or order is created by this tool; it only returns information. Preferred input: `domains`, 1 to 200 fully-qualified names (e.g. ['acme.com', 'acme.io']); results cover exactly those domains, with no suggestions or expansion. Fallback input: `query`, free text (one or more names, comma- or space-separated); names given without a TLD are expanded to popular TLDs (com/io/ai/co/net). Each result includes whether the domain is available, whether it is a premium name, the registration price and the renewal price. Both prices are totals for one full registration term of that ending, not per-year rates: one year on most endings, but two years on .ai, whose registry mandates a two-year term. Do not divide or multiply a returned price by a number of years. Available non-premium results also carry a `checkout_url` the user can open in a browser to register the domain on justdomain.ai if they choose to. Premium names cannot be registered through Just Domain yet and carry no `checkout_url`.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | – | – | Fully-qualified domains to check, e.g. ['acme.com', 'acme.io', 'acme.ai']. Each entry must include the TLD. Maximum 200 per request. Preferred over `query`. |
| query | – | – | Free-text fallback when exact FQDNs aren't known: one or more names, comma- or space-separated. Names without a TLD are expanded to popular TLDs (com/io/ai/co/net). Ignored when `domains` is provided. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | Available domains the caller did not ask about, offered only when every requested domain came back unavailable. Same label the caller typed, on a different ending; nothing is invented and nothing her… |
| component_hint | string | – | – |
| domains | array | yes | The exact domains requested by the caller, echoed back. |
| error | – | – | Set when the search could not be completed (e.g. invalid query, provider failure). |
| error_message | – | – | – |
| next_action | string | – | – |
| results | array | yes | – |
| warnings | array | – | – |
No examples provided.
What is the Just Domain MCP server?
Just Domain is an MCP server listed in the public MCP registry as ai.justdomain/just-domain. Search domain availability and pricing, and check if a domain can transfer in, from chat. This page covers its hosted endpoint (https://mcp.justdomain.ai/).
Is the Just Domain MCP server safe to use?
Just Domain scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Just Domain MCP server expose?
Just Domain exposes 2 tools: search_domains, check_domain_transfer. Their descriptions and schemas cost roughly 909 tokens of context every time the server is loaded.
Does the Just Domain MCP server require authentication?
No. We connected to Just Domain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Just Domain MCP server still maintained?
Just Domain is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.