F
licenseA
qualityD
maintenanceProvides comprehensive DNS lookup capabilities including A, AAAA, MX, TXT, NS, SOA, CNAME, SRV, CAA, DNSSEC records, reverse DNS lookups, and bulk queries for multiple domains or IPs.
4
-
dns-check
by ai.kaiv
Server Details
Live DNS lookups for agents: A/MX/TXT/SPF/CNAME/PTR with TTLs and DNSSEC, via Google Public DNS.
Ownership verified
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
1 toolresolve_dnsResolve DnsARead-onlyIdempotentInspect
Resolve any DNS record live via Google Public DNS. Answers: is DNS propagated? What are the MX/TXT/SPF/DKIM records? Where does this CNAME point? For reverse lookup pass name=.in-addr.arpa with type=PTR (e.g. 90.57.149.3.in-addr.arpa for 3.149.57.90). Returns Status (0 = NOERROR, 3 = NXDOMAIN), Answer records with TTLs, and the AD flag for DNSSEC validation.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| do | No | Set 'true' to include DNSSEC records (RRSIG) in the response | |
| name | Yes | Domain name to resolve, e.g. 'kaiv.ai' (or reversed IP + .in-addr.arpa for PTR) | |
| type | No | Record type: A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, PTR, SRV. Default A. | A |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive hints. The description adds valuable behavioral details such as the Status codes (NOERROR vs NXDOMAIN), the inclusion of Answer records with TTLs, and the AD flag for DNSSEC, which are not in the annotations. This enriches the agent's understanding of output and behavior.
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 front-loaded with the core purpose and use cases, followed by a concrete reverse-lookup example. Every sentence earns its place—no repetition, no fluff, and it is compact for the info it delivers.
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?
With no output schema, the description explicitly explains the response structure (Status, Answer with TTLs, AD flag). It also covers all three parameters, including the 'do' option for DNSSEC. The tool is well-specified for an agent to call correctly without missing information.
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 description coverage is 100%, with each parameter already documented. The description adds an example for PTR (reversed IP) but does not significantly expand on parameter meanings beyond what the schema provides. Baseline 3 applies because the schema already carries the semantics.
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 starts with a specific verb ('Resolve') and resource ('any DNS record') and immediately clarifies the purpose via concrete use cases ('is DNS propagated?', MX/TXT/SPF/DKIM records, CNAME target). It leaves no ambiguity about what the tool does and is well-distinguished from any potential alternatives.
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?
It clearly states when to use the tool with examples and gives specific instruction for reverse lookup (PTR with reversed IP). However, it does not explicitly mention when not to use it or any alternative tools, though none are listed as siblings. The context is strong enough to guide typical usage.
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. Dates show when Glama detected each change.
1 tool update
- Changed
resolve_dns2 fields changed- added
Input schema / properties / type / defaultAdded value: +"A" - added
Input schema / properties / type / enumAdded value: +[ + "A", + "AAAA", + "MX", + "TXT", + "NS", + "CNAME", + "SOA", + "CAA", + "PTR", + "SRV" +]
1 tool update
- First observed
resolve_dns
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Look up DNS information for any domain to troubleshoot issues and gather insights. Get fast, relia…
Unlock the power of DNS lookups with our DNS Lookup service using Google DNS-over-HTTPS. Whether
Scan, fix and verify DNS: SPF, DMARC, DKIM, propagation, DNS health, expiry. Validated fixes.
Live DNS, email-auth and redirect checks, HTTP security headers, uptime history, PC hardware prices.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform pay-per-call DNS record lookups (A, AAAA, MX, TXT, CNAME, NS, SOA, SRV) via Cloudflare DNS-over-HTTPS, with x402 micropayments and no API key or signup.MIT
- AlicenseNot gradedqualityCmaintenanceEnables DNS record lookups for types like A, MX, TXT, and CNAME, bulk queries of all major record types, and reverse DNS resolution from IP addresses to hostnames.5MIT
- FlicenseNot gradedqualityDmaintenanceA comprehensive DNS query server that enables querying all types of DNS records, including A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, SRV, CAA, and DNSSEC checks, as well as advanced tools like WHOIS-style lookup and DNS delegation tracing.1-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.3/5.0
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is singular and clearly defined, making misselection impossible.
Naming Consistency5/5
A single tool name follows no conflicting pattern, so consistency is trivially maintained. The verb_noun style ('resolve_dns') is clear and descriptive, aligning with best practices.
Tool Count3/5
At one tool, the server feels minimal and may lack depth for more complex DNS workflows. While the single tool is well-scoped, the count is at the borderline of what feels too thin for a full-featured server.
Completeness4/5
The tool covers the core DNS resolution domain comprehensively—any record type, reverse lookups, and DNSSEC status. It omits peripheral features like batch lookups or multi-server comparison, but for its stated purpose it is essentially complete.