A
license-
qualityD
maintenanceEnables buying and managing internet domains directly from AI chat, including availability checks, registration, DNS configuration, email forwarding, and AI bot tracking.
Last updated
MIT
Just Domain
Server Details
Search domain availability and pricing, straight from chat — then open a link to register.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- just-done/just-domain-mcp
- GitHub Stars
- 0
- Server Listing
- Just Domain MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.9/5.0
Tool DescriptionsA
Average 4.9/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion between tools.
Naming Consistency5/5
With a single tool, naming consistency is not applicable but is inherently consistent.
Tool Count4/5
One tool for read-only domain lookup is appropriate for a focused service, though additional tools for registration or management could be present.
Completeness5/5
The tool fully covers the server's declared purpose of checking domain availability and pricing, including providing a checkout URL for registration.
Available Tools
1 toolsearch_domainsSearch domain availabilityARead-onlyIdempotentInspect
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–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 first-year registration price, and the annual renewal price. Available results also carry a checkout_url the user can open in a browser to register the domain on justdomain.ai if they choose to.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | 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. | |
| domains | No | 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`. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| error | No | Set when the search could not be completed (e.g. invalid query, provider failure). |
| domains | Yes | The exact domains requested by the caller, echoed back. |
| results | Yes | |
| warnings | No | |
| next_action | No | |
| error_message | No | |
| component_hint | No |
Tool Definition Quality
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description adds important behavioral details: the exact scope of results, TLD expansion for `query`, and the presence of a `checkout_url` in available results. It reinforces the read-only nature and discloses output fields, which is helpful for the agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured: it starts with the core read-only purpose, then explains preferred vs fallback input, and ends with output details. Every sentence adds value and there is no redundancy or fluff.
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?
Given the presence of an output schema and annotations, the description fully covers input behavior, output fields, and the key caveat of not creating orders. There are no siblings, so no alternative guidance is needed, making it complete for this tool.
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?
The input schema already provides rich descriptions for both parameters, so the baseline is 3. The description adds the nuance that `domains` results 'cover exactly those domains, with no suggestions or expansion,' which is not in the schema. This small addition justifies a 4.
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?
The description clearly states the tool is a 'Read-only availability and pricing lookup for domain names' and explicitly says 'No purchase or order is created by this tool.' This gives a specific verb (lookup), resource (domain names), and scope (availability/pricing), making the purpose unmistakable even without siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly distinguishes the preferred input (`domains`) for exact FQDNs from the fallback input (`query`) for free-text, explaining when to use each and that `query` expands TLDs. It also conveys a when-not by clarifying that no purchase/order is created, so agents know this is for checking only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceSearch, register, and manage domain names through natural conversation with AI assistants.Last updated2MIT
- Alicense-qualityCmaintenanceEnables checking domain availability and registration prices across multiple TLDs and providers. Users can find available domain names and compare pricing through natural language.Last updated249MIT
- Alicense-qualityDmaintenanceEnables AI assistants to check domain availability across multiple TLDs with real-time pricing, brainstorm creative domain names, analyze domains for brandability and SEO potential, and search for domains by price and category without CAPTCHAs.Last updated183MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.