F
license-
qualityC
maintenanceEnables AI assistants to query domain expiration data from domain-monitor.io, with tools for listing domains, checking expiry, and adding new domains.
1
domain-age-pro
by com.jojapi
Server Details
Domain Age PRO: Check the domain age using fastest api response. On the JoJ API marketplace.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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
C2.4/5.0
Tool DescriptionsC
Average 2.2/5 across 1 of 1 tools scored.
Server CoherenceB
Disambiguation5/5
With only one tool, there is no possibility of confusion with other tools. The single tool's purpose is clearly described as retrieving domain age.
Naming Consistency1/5
The tool name 'get_getAge' is redundant (double 'get') and mixes verb-with-noun awkwardly. It lacks any consistent pattern and is confusing despite a clear description.
Tool Count2/5
Having only one tool for a domain-age service is too few to be robust. Users might expect additional operations like domain validation or WHOIS details, but the surface is minimal.
Completeness4/5
The tool fulfills its stated purpose of fetching domain age completely. While additional domain-related operations could be imagined, for a focused age-lookup service, the coverage is adequate.
Available Tools
1 toolget_getAge/getAge/CInspect
Get domain age Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No |
Tool Definition Quality
C2.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description lacks explicit behavioral disclosures beyond the basic 'get' operation. While it mentions a cost per call (1 Credit), it does not elaborate on side effects, permissions, rate limits, or error handling, which are critical for a tool without annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of only one sentence, but it awkwardly merges the core functionality with billing information, which could be better separated. The structure lacks clear segmentation, making it less readable than it could be.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description fails to provide essential context such as the expected return value, potential limitations, or how the tool fits into a larger workflow. With no output schema and minimal details, it is insufficient for a user to understand the tool's full behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema lists a single parameter 'domain' without any description, and the tool description does not clarify its meaning, format, or constraints. The example 'google.com' is present in the schema but not explained, so parameter semantics are virtually undefined.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the primary function as 'Get domain age', which is a specific verb and resource. However, the inclusion of 'Billing per call: 1 Credits' is somewhat tangential and could be confused with the core purpose, slightly reducing clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or conditions for its usage. It simply states the action without contextualizing its appropriate usage.
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
- AlicenseCqualityDmaintenanceProvides a comprehensive suite of SEO and web utility tools for domain analysis, keyword tracking, SERP data, and technical site audits. It enables users to perform various tasks such as checking domain age, WHOIS information, and website technology stacks.34MIT
- 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.203MIT
- AlicenseAqualityDmaintenanceEnables AI agents to check domain availability, perform batch domain lookups, and generate intelligent domain name suggestions across multiple TLDs using WHOIS integration.43MIT