Skip to main content
Glama
robyroro

osint-mcp-server

by robyroro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

DNS lookup

dns_lookup
Read-onlyIdempotent

Fetch live DNS records for a domain, such as A, MX, TXT, and NS. Use for OSINT reconnaissance to map infrastructure and validate domain configurations.

Instructions

Live DNS records for a domain, as {"records": {"A": [...], "MX": [...]}}. Types with no records are left out, a type that doesn't answer within 5s shows "", and a domain that doesn't exist returns an NXDOMAIN error.

Use for raw records. email_security already reads and grades the SPF / DMARC / DKIM TXT records, and recon_domain includes this lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name, e.g. "example.com". A full URL works too, only the hostname is used.
nameserverNoIP of the resolver to ask, e.g. "1.1.1.1", or one of the domain's own nameservers to skip caches. Defaults to the system resolver.
record_typesNoRecord types to query, e.g. ["A", "MX", "TXT"]. Defaults to A, AAAA, CNAME, MX, NS, TXT, SOA and CAA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / domain / description
      Added value: +"Domain name, e.g. \"example.com\". A full URL works too, only the hostname is used."
    • addedInput schema / properties / nameserver / description
      Added value: +"IP of the resolver to ask, e.g. \"1.1.1.1\", or one of the domain's own nameservers to skip caches. Defaults to the system resolver."
    • addedInput schema / properties / record_types / description
      Added value: +"Record types to query, e.g. [\"A\", \"MX\", \"TXT\"]. Defaults to A, AAAA, CNAME, MX, NS, TXT, SOA and CAA."
  2. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds behavior beyond them: omitted empty types, a 5s timeout rendered as "<timeout>", NXDOMAIN on missing domains, and the return envelope shape. That is exactly the extra context annotations cannot express.

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?

Front-loads the return contract and edge cases, then closes with a single-sentence routing note. Every sentence carries information; no filler.

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?

No output schema exists, yet the description supplies the response envelope and the two important exceptional outcomes (timeout and NXDOMAIN). For a 3-param read-only lookup this is complete.

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%, so the schema already documents domain, nameserver, and record_types with examples and defaults. The description adds no parameter-level syntax beyond that, so the baseline 3 is appropriate.

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?

States a specific verb+resource ('Live DNS records for a domain') and immediately distinguishes itself from siblings by naming email_security and recon_domain. An agent can tell what it returns and how it differs from the alternatives without opening any schema.

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?

'Use for raw records' is an explicit when-to-use directive, followed by the condition that routes the agent elsewhere ('email_security already reads and grades SPF/DMARC/DKIM'). This is textbook routing guidance with named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools