Skip to main content
Glama

Just Domain

by ai.justdomain
OverviewDiscussionsAdmin

Server Details

Check a domain name, both prices and whether it can transfer in. You register it on justdomain.ai.

Ownership verified
Status
Healthy
Uptime
99.9% over 71 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
just-done/just-domain-mcp
GitHub Stars
0
Server Listing
Just Domain MCP Server

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a genuinely different question: availability/price of a new name, eligibility/price of transferring an owned domain, and trademark conflicts for a proposed name. The check_trademark description explicitly redirects availability questions to search_domains, and check_domain_transfer is scoped to already-owned domains, so boundaries are crisp.

Naming Consistency5/5

All three names are snake_case verb_noun (check_domain_transfer, check_trademark, search_domains). The check_/search_ verb split is semantically motivated rather than arbitrary, and the noun always identifies the resource being inspected.

Tool Count4/5

Three tools is lean but each one covers a distinct, non-trivial workflow with substantial payloads (blockers, verdict, per-domain pricing). For a registrar's read-only lookup surface this is reasonable, though the set is close to the thin/borderline threshold given the breadth of the domain.

Completeness3/5

The read-only research loop (is it available, what does it cost, can I transfer it, is the name trademark-safe) is closed and well cross-referenced, with checkout/transfer URLs handling handoff. However, there is no tool for a user's own portfolio, renewals, DNS state of owned domains, or any write operation, so agents will hit dead ends for anything past pre-purchase research.

Available Tools

3 tools
check_domain_transferCheck whether a domain can transfer to Just DomainA
Read-only
Inspect

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 self-service: the owner checks it and pays at https://justdomain.ai/transfer, pasting the authorization code there, and a transfer that does not complete is refunded in full. This tool tells the user whether the domain is eligible to move and what one full term would cost; hand over transfer_url, which opens that page for this domain in the owner's browser. Nothing is paid or ordered inside the chat. 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 does not return, accept, or hint at an authorization (EPP) code, and there is no agent path to unlocking a domain or to having a code issued, here or through any other Just Domain surface. An auth code is a bearer credential for the domain and a chat transcript is not a place to put one. Do not ask the user for a code, do not offer to hold or relay one, and never claim you can unlock or move the domain yourself.

NameRequiredDescriptionDefault
domainYesOne 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.

Output Schema

NameRequiredDescription
tldYes
priceNoNull when the registrar's price list could not be read. Never estimate a domain transfer price yourself.
readyYesTRUE 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 rather than as a green light.
domainYes
sourceYesWhich public sources actually answered on this request.
blockersNoWhat stands between this domain and a transfer, most blocking first. An EMPTY list is the only thing that means ready.
next_stepYesOne sentence you can say to the user about what happens next, already matched to this domain's state.
registrarYesWho sponsors the domain today, as the REGISTRY reports it.
supportedYesWhether Just Domain can accept this ENDING at all. Says nothing about this particular domain - read `blockers` for that.
checked_atYesISO-8601 instant these facts were read.
nameserversNo
transfer_urlYesThe page on justdomain.ai a PERSON opens in a browser to take this further. The handoff out of the chat.
dns_continuityYesDoes 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.
auth_code_policyYesConstant. The rule about authorization (EPP) codes, restated in the payload so it travels with the answer. Follow it.

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds extensive behavior beyond annotations: public RDAP and price-list sources only, no authentication, no account reads, and nothing ordered or changed. It explains blockers semantics, unknown codes, RDAP failure meaning, total-term pricing, .ai two-year terms, projected expiry, self-service transfer flow, and strict no-auth-code/no-unlock limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and safety, and most sentences carry operational meaning. It is somewhat long and repeats the no-payment/no-auth-code boundary, but the repetition is mostly security-relevant for a transfer tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a read-only precheck with an output schema: it explains the critical returned fields (`blockers`, `source.rdap`, `price`, `term_note`, `expected_new_expiry`, `transfer_url`) and the self-service boundaries. An agent has enough context to call and present results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema already explains that `domain` must be one fully-qualified domain, not a bare label or list. The description reinforces ownership context but adds little syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: a read-only transfer precheck for ONE domain the user already owns at another registrar. It also clarifies scope and outcome, distinguishing it from search or trademark siblings without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage context: one already-owned domain at another registrar, with eligibility, blockers, cost, and DNS survival. It does not explicitly name when to use search_domains or check_trademark instead, so it falls short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

check_trademarkCheck a name against trademark registersA
Read-only
Inspect

Read-only trademark check for ONE proposed name, answered by Open Trademarks (opentrademarks.org) from the US, EU and Israeli trademark registers. Nothing is filed, reserved, watched or paid for. Optional goods (free text, mapped to Nice classes), classes (Nice classes 1 to 45) and registers (a subset of us, eu, il; all three by default) narrow the check. Read verdict first. exact_live_mark and similar_live_marks name the marks behind them in conflicts, each with its register, number and how it matched. no_live_match means no live mark matched in the registers that were read: a positive signal, not clearance. not_checked means no register in this check has been read yet, so it is NOT a verdict: do not call the name clear or taken on it. registers gives each register's read date, and a register with no loaded_at was not checked at all. Never tell a user a name is clear unless it was checked during this conversation and every register in the answer was read today or yesterday. Quote notice as written: a register search is not legal advice. This checks trademarks only, not whether a domain is available; use search_domains for that.

NameRequiredDescriptionDefault
nameYesThe proposed name, as the user would use it (e.g. 'Acme' or 'koh-i-noor'). One name per call.
goodsNoOptional: what the name will be used for, in plain words (e.g. 'accounting software'). Open Trademarks maps it to Nice classes.
classesNoOptional: Nice classes to check, each 1 to 45 (e.g. [9, 42]).
registersNoWhich registers to read: a subset of `us`, `eu` and `il`. All three when left out.

Output Schema

NameRequiredDescription
deadNo
queryYes
noticeYesThe answer's own caveat. Quote it as written.
verdictYes`exact_live_mark`, `similar_live_marks`, `no_live_match`, or `not_checked`. `not_checked` means no register in this check has been read yet: it is NOT a verdict, so never call the name clear or taken on it. `no_live_match` is a positive signal, not clearance.
conflictsNoThe live marks behind the verdict, most relevant first.
registersNoEvery register in the check with its read date. Do not tell a user a name is clear unless every register here was read today or yesterday.
generated_atNoWhen Open Trademarks built this answer.
other_classesNoLive marks that match in classes other than the ones checked.

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnly/openWorld annotations: 'Nothing is filed, reserved, watched or paid for' discloses side effects, and the description explains staleness handling ('a register with no loaded_at was not checked at all'), the today-or-yesterday freshness rule, and the requirement to quote `notice` verbatim as non-legal-advice. This is unusually rich behavioral context for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the one-line purpose and side-effect disclaimer before parameter and result guidance, and every sentence carries operational weight. It is dense and runs long, with the verdict-field guidance occupying a large share of the text, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still explains how to read the key fields (verdict, exact_live_mark, similar_live_marks, conflicts, registers.loaded_at) and warns that `not_checked` is not a verdict. Combined with the freshness and legal-notice rules, an agent has everything needed to call and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by framing all three optional parameters as narrowers of the check, noting that `goods` is free text mapped to Nice classes and that `registers` defaults to all three. It still doesn't clarify precedence when `goods` and `classes` are both supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read-only trademark check for ONE proposed name') plus the data source (Open Trademarks) and register scope (US, EU, IL). The 'ONE name per call' scope and the explicit contrast with search_domains let an agent separate it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use context and an explicit exclusion ('This checks trademarks only, not whether a domain is available; use search_domains for that'), plus rules about when a result may be reported to a user. It never distinguishes itself from the sibling search_trademarks, so the routing guidance is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_domainsSearch domain availabilityA
Read-onlyIdempotent
Inspect

Use this when the user asks whether a domain name is available or what it costs to register: call it directly with the names, with no account and no confirmation needed. 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.

NameRequiredDescriptionDefault
queryNoFree-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.
domainsNoFully-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`.

Output Schema

NameRequiredDescription
errorNoSet when the search could not be completed (e.g. invalid query, provider failure).
domainsYesThe exact domains requested by the caller, echoed back.
resultsYes
warningsNo
next_actionNoAn instruction for the assistant reading this response, or the string 'none' when there is nothing extra to do. It is set only when no requested domain and no alternative in this response can be registered through Just Domain. When it is not 'none', carry it out in this same turn before replying to the user; it is written to be executable as-is.
alternativesNoAvailable 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 here duplicates a name in `results`. Every entry is available, non-premium and carries a `checkout_url`, so it can be offered to the user directly. Empty is not an error. It means one of three things: recovery is switched off for this deployment, or the search was not a dead end, or the same label is taken on the other endings too, which is the normal outcome for a common dictionary word. Do not tell the user that other endings were checked unless this list is non-empty. Do not re-check these; they were checked live in this same call.
error_messageNo
component_hintNo

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnly/destructive annotations: no account or confirmation required, no purchase or order is created, pricing is a total per registration term (with the .ai two-year exception and an explicit warning not to divide by years), and premium names cannot be registered and lack a checkout_url.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger and the no-purchase guarantee, then structured into preferred/fallback inputs and result semantics. It is long and the opening sentence mildly repeats the read-only framing, so a little could be trimmed, but nearly every sentence carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description adds the interpretive layer an agent needs: what each result field means, how prices are totalled, and why premium results lack a checkout_url. Nothing needed to call or interpret the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: `domains` results cover exactly those names with no suggestions or expansion, and `query` without a TLD is expanded to a named TLD list and ignored when `domains` is set. It stops short of restating edge-case validation like null handling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read-only availability and pricing lookup for domain names') and scopes it precisely to the user question it answers. It is clearly distinguishable from sibling checks like check_domain_transfer and check_trademark, which concern different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger ('when the user asks whether a domain name is available or what it costs to register') and removes friction ('no account and no confirmation needed'). It also specifies preferred vs fallback input paths, though it never explicitly names the sibling tools or when-not to use this one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Removedsearch_trademarks
  2. 3 tool updates
    • Changedcheck_domain_transfer1 field changed
      • changedOutput schema / properties / blockers / items / properties / code / description
        Previous value: -"Stable code: 'locked', 'within_60_days', 'redemption', 'expired', 'tld_unsupported', 'premium', 'not_registered', 'pending_transfer', 'pending_delete', or 'unknown'. If you do not recognise a code, render `detail` verbatim - never drop a blocker you have no wording for."New value: +"Stable code: 'locked', 'within_60_days', 'redemption', 'expired', 'tld_unsupported', 'premium', 'not_registered', 'pending_transfer', 'pending_delete', 'dns_plan_unavailable', or 'unknown'. If you do not recognise a code, render `detail` verbatim - never drop a blocker you have no wording for."
    • Addedcheck_trademark
    • Addedsearch_trademarks
  3. 1 tool update
    • Changedsearch_domains2 fields changed
      • removedOutput schema / properties / next_action / const
        Removed value: -"none"
      • addedOutput schema / properties / next_action / description
        Added value: +"An instruction for the assistant reading this response, or the string 'none' when there is nothing extra to do. It is set only when no requested domain and no alternative in this response can be registered through Just Domain. When it is not 'none', carry it out in this same turn before replying to the user; it is written to be executable as-is."
  4. 2 tool updates
    • Addedcheck_domain_transfer
    • Changedsearch_domains2 fields changed
      • addedOutput schema / properties / alternatives
        Added value: +{
+  "description": "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 here duplicates a name in `results`. Every entry is available, non-premium and carries a `checkout_url`, so it can be offered to the user directly. Empty is not an error. It means one of three things: recovery is switched off for this deployment, or the search was not a dead end, or the same label is taken on the other endings too, which is the normal outcome for a common dictionary word. Do not tell the user that other endings were checked unless this list is non-empty. Do not re-check these; they were checked live in this same call.",
+  "items": {
+    "properties": {
+      "available": {
+        "type": "boolean"
+      },
+      "checkout_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "URL on the Just Domain website where the user completes payment. Set for available domains we can actually register; null for unavailable ones, for premium names (the checkout API refuses them), and for endings whose registry requires registrant data we cannot supply yet. The MCP tool handler fills this in after the bare service call so the UI widget's Buy button can open checkout directly in one click."
+      },
+      "fqdn": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "premium": {
+        "default": false,
+        "type": "boolean"
+      },
+      "price": {
+        "anyOf": [
+          {
+            "properties": {
+              "amount_minor": {
+                "description": "Amount in the smallest currency unit (e.g. cents).",
+                "type": "integer"
+              },
+              "currency": {
+                "description": "ISO-4217 currency code.",
+                "maxLength": 3,
+                "minLength": 3,
+                "type": "string"
+              },
+              "formatted": {
+                "description": "Human-readable price, e.g. '$12.99'.",
+                "type": "string"
+              }
+            },
+            "required": [
+              "amount_minor",
+              "currency",
+              "formatted"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Registration price: the total for ONE full registration term of this ending, not a per-year rate. One year on most endings; two years on .ai, whose registry mandates a two-year term."
+      },
+      "renewal_price": {
+        "anyOf": [
+          {
+            "properties": {
+              "amount_minor": {
+                "description": "Amount in the smallest currency unit (e.g. cents).",
+                "type": "integer"
+              },
+              "currency": {
+                "description": "ISO-4217 currency code.",
+                "maxLength": 3,
+                "minLength": 3,
+                "type": "string"
+              },
+              "formatted": {
+                "description": "Human-readable price, e.g. '$12.99'.",
+                "type": "string"
+              }
+            },
+            "required": [
+              "amount_minor",
+              "currency",
+              "formatted"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Renewal price: the total for ONE further registration term, on the same basis as `price`. What a later term would cost at today's rate, not a figure anyone has been charged or quoted for a specific renewal. An owner renews, and turns auto-renew on or off, on their own dashboard at https://justdomain.ai/dashboard, which is the only authoritative source for one domain's renewal state."
+      },
+      "requires_additional_data": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Does this ending's registry demand registrant data beyond standard contact details - a nexus declaration, a national ID, a professional credential? TRI-STATE: true / false / null = we do not know. Just Domain cannot collect or submit that data yet, so a true (or unknown) value means the name is reported honestly but carries no `checkout_url`."
+      },
+      "status": {
+        "description": "Raw provider status, e.g. 'free', 'active', 'premium'.",
+        "type": "string"
+      },
+      "term_years": {
+        "default": 1,
+        "description": "Length in years of ONE registration term for this ending, and therefore the period `price` and `renewal_price` each cover. 1 on most endings; 2 on .ai, whose registry mandates a two-year term with no one-year option. Read this before describing any price as annual.",
+        "type": "integer"
+      },
+      "tld": {
+        "type": "string"
+      },
+      "warnings": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "fqdn",
+      "name",
+      "tld",
+      "available",
+      "status"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
      • changedOutput schema / properties / results / items / properties / renewal_price / description
        Previous value: -"Renewal price: the total for ONE further registration term, on the same basis as `price`. What a later term would cost at today's rate; Just Domain does not yet run renewals."New value: +"Renewal price: the total for ONE further registration term, on the same basis as `price`. What a later term would cost at today's rate, not a figure anyone has been charged or quoted for a specific renewal. An owner renews, and turns auto-renew on or off, on their own dashboard at https://justdomain.ai/dashboard, which is the only authoritative source for one domain's renewal state."
  5. 1 tool update
    • Changedsearch_domains2 fields changed
      • changedOutput schema / properties / results / items / properties / checkout_url / description
        Previous value: -"URL on the Just Domain website where the user completes payment. Set for available domains we can actually register; null for unavailable ones and for premium names, which the checkout API refuses. The MCP tool handler fills this in after the bare service call so the UI widget's Buy button can open checkout directly in one click."New value: +"URL on the Just Domain website where the user completes payment. Set for available domains we can actually register; null for unavailable ones, for premium names (the checkout API refuses them), and for endings whose registry requires registrant data we cannot supply yet. The MCP tool handler fills this in after the bare service call so the UI widget's Buy button can open checkout directly in one click."
      • addedOutput schema / properties / results / items / properties / requires_additional_data
        Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Does this ending's registry demand registrant data beyond standard contact details - a nexus declaration, a national ID, a professional credential? TRI-STATE: true / false / null = we do not know. Just Domain cannot collect or submit that data yet, so a true (or unknown) value means the name is reported honestly but carries no `checkout_url`."
+}
  6. 1 tool update
    • Changedsearch_domains3 fields changed
      • changedOutput schema / properties / results / items / properties / price / description
        Previous value: -"First-year registration price."New value: +"Registration price: the total for ONE full registration term of this ending, not a per-year rate. One year on most endings; two years on .ai, whose registry mandates a two-year term."
      • changedOutput schema / properties / results / items / properties / renewal_price / description
        Previous value: -"Annual renewal price (charged each year after registration)."New value: +"Renewal price: the total for ONE further registration term, on the same basis as `price`. What a later term would cost at today's rate; Just Domain does not yet run renewals."
      • addedOutput schema / properties / results / items / properties / term_years
        Added value: +{
+  "default": 1,
+  "description": "Length in years of ONE registration term for this ending, and therefore the period `price` and `renewal_price` each cover. 1 on most endings; 2 on .ai, whose registry mandates a two-year term with no one-year option. Read this before describing any price as annual.",
+  "type": "integer"
+}
  7. 1 tool update
    • Changedsearch_domains1 field changed
      • changedOutput schema / properties / results / items / properties / checkout_url / description
        Previous value: -"URL on the Just Domain website where the user completes payment. Set for available domains; null for unavailable. The MCP tool handler fills this in after the bare service call so the UI widget's Buy button can open checkout directly in one click."New value: +"URL on the Just Domain website where the user completes payment. Set for available domains we can actually register; null for unavailable ones and for premium names, which the checkout API refuses. The MCP tool handler fills this in after the bare service call so the UI widget's Buy button can open checkout directly in one click."
  8. 1 tool update
    • Changedsearch_domains9 fields changed
      • addedInput schema / properties / domains / anyOf
        Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 200,
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / properties / domains / default
        Added value: +null
      • changedInput schema / properties / domains / description
        Previous value: -"Fully-qualified domains to check, e.g. ['acme.com', 'acme.io', 'acme.ai']. Each entry must include the TLD. Maximum 200 per request."New value: +"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`."
      • removedInput schema / properties / domains / items
        Removed value: -{
-  "type": "string"
-}
      • removedInput schema / properties / domains / maxItems
        Removed value: -200
      • removedInput schema / properties / domains / minItems
        Removed value: -1
      • removedInput schema / properties / domains / type
        Removed value: -"array"
      • addedInput schema / properties / query
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "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."
+}
      • removedInput schema / required
        Removed value: -[
-  "domains"
-]
  9. 1 tool update
    • First observedsearch_domains

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources