A
licenseA
qualityD
maintenanceEnables domain lookups using the RDAP protocol, returning structured registration data, nameservers, and contacts from over 50 supported TLDs.
1
10
1
MIT
launch-record-lookup
Server Details
Look up a domain's public Website Launches launch record, owner verification & trust context.
- 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
A4.5/5.0
Tool DescriptionsA
Average 4.8/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly distinct by default.
Naming Consistency5/5
With a single tool, naming consistency is inherently perfect. The tool name 'lookup_launch_record' follows a clear verb_noun pattern.
Tool Count3/5
Having only one tool feels thin for a domain that could support additional operations like searching or listing records. However, for a very narrowly scoped lookup service, one tool can be appropriate, making it borderline.
Completeness2/5
The tool only supports a single lookup operation with no ability to search, list, or manage launch records. This creates significant gaps for agents needing broader access, limiting the tool surface severely.
Available Tools
1 toollookup_launch_recordLook up a launch recordARead-onlyInspect
Look up the public Website Launches launch record for a single domain. Returns launch timing, owner verification status, milestone summary, public trust context, and a public record URL. Single domain only; does not search, list, discover, or export websites. Hosting, registrar, and location are secondary details — only surface them if the user explicitly asks.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | A single website domain or URL, such as example.com or https://www.example.com/about. Provide exactly one domain — not a list, and not a search query. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| domain | No | |
| status | Yes | |
| owner_status | No | |
| public_links | No | |
| launch_record | No | |
| trust_context | No | |
| basic_identity | No | |
| technical_details | No | |
| recommended_response | Yes |
Tool Definition Quality
A4.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond annotations (readOnlyHint, openWorldHint, destructiveHint) by detailing what information is returned and what is excluded. However, it does not mention any potential rate limits, authentication requirements, or error conditions, which would have made it fully transparent.
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 three sentences long, with the first sentence immediately stating purpose and return values. Every sentence contributes essential information without 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 simple one-parameter tool with full schema coverage, an output schema, and clear annotations, the description covers all necessary aspects: what the tool does, what it returns, and constraints. No gaps are evident.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description reinforces the schema's parameter description for 'domain' by repeating the requirement for a single domain and clarifying it should not be a list or search query. This adds practical context beyond the schema's structured definition.
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 looks up a 'public Website Launches launch record for a single domain' and lists specific return fields. It explicitly distinguishes from search, list, discover, or export operations, making the purpose unmistakable.
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 provides explicit guidance: 'Single domain only; does not search, list, discover, or export websites.' It also advises only surfacing secondary details (hosting, registrar, location) if explicitly requested, which helps the AI agent decide when to use this tool versus alternatives.
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
- Flicense-qualityBmaintenancePassive website security and trust auditor that checks for security, SEO, AI surface, email, and other exposures, producing a score and remediation plan.
- Flicense-qualityFmaintenancePay-per-call API that verifies whether a domain belongs to a real business. Returns a verdict (real/likely_real/uncertain/likely_fake/fake), a 0-100 score, and signals (WHOIS via RDAP, SSL via Certificate Transparency, homepage LLM judgment, contacts, social) — for KYB, vendor screening, fraud checks, and lead qualification.
- Alicense-qualityBmaintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.5MIT