Domain Availability Grounding Data

Overview

Domain Availability is a domain check API: pass one domain name and it reports whether the domain is available to register, plus its creation and expiry dates when it is already taken. It queries the registry over RDAP, falling back to WHOIS, at the time of the request. Paid plans also get the TLD's registration, renewal and transfer price range across registrars, refreshed weekly, and a flag for names the registry likely prices as premium.

Live Test Domain Availability Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as DomainAvailabilityGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "DomainAvailabilityGroundingData",
  "arguments": {
    "domain": "myspace.com"
  }
}

You do not name the tool yourself; the model picks it. Asking about myspace.com in the terms this source covers is enough for it to reach for DomainAvailabilityGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "myspace.com",
    "available": false,
    "owner": {
      "registrar": "GoDaddy.com, LLC",
      "createdDate": "1996-02-22T05:00:00Z",
      "expiryDate": "2029-02-23T05:00:00Z"
    },
    "source": "rdap",
    "pricing": {
      "tld": "com",
      "currency": "USD",
      "registration": {
        "low": 11.08,
        "high": 11.25
      },
      "renewal": {
        "low": 11.08,
        "high": 11.25
      },
      "transfer": {
        "low": 11.08,
        "high": 11.25
      },
      "sources": 2,
      "premiumLikely": null,
      "premiumReason": null,
      "updatedAt": "2026-10-18T10:00:00.000Z"
    },
    "lifecycle": "registered",
    "eppStatus": [
      "client delete prohibited",
      "client renew prohibited",
      "client transfer prohibited",
      "client update prohibited"
    ],
    "nameservers": [
      "ns-cloud-a1.googledomains.com",
      "ns-cloud-a2.googledomains.com",
      "ns-cloud-a3.googledomains.com",
      "ns-cloud-a4.googledomains.com"
    ],
    "isParked": false,
    "isForSale": false,
    "parkingService": null
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at available: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Business Name Generators

When entrepreneurs test company names, business formation apps verify if matching dot-com addresses are unregistered before finalizing entity paperwork.

Domain Reseller Storefronts

Show buyers instant availability flags and registration expiry dates directly inside custom search bars for registrar and web hosting portals.

Trademark Defense Audits

Legal teams scan potential brand collisions across key top-level domains, inspecting registration dates to establish prior use or bad-faith squatting.

Agency Rebranding Workflows

Filter out claimed domains early during client naming sprints so design studios pitch only project handles that can actually be acquired.

Other ways to use Domain Availability Grounding Data

Set up Domain Availability Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Domain Data: