Skip to main content
Glama
badchars

osint-mcp-server

by badchars

vt_domain

Analyze domain reputation and security data using VirusTotal to identify threats, check detection statistics, and review DNS records for reconnaissance.

Instructions

VirusTotal domain analysis: reputation score, detection stats, categories, registrar, DNS records. Requires VT_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to analyze

Implementation Reference

  • Handler implementation for the vt_domain tool.
    export async function vtDomain(domain: string, apiKey: string): Promise<VtDomainResult> {
      const cacheKey = `vt:domain:${domain}`;
      const cached = cache.get(cacheKey);
      if (cached) return cached;
    
      const data = await vtFetch(`/domains/${encodeURIComponent(domain)}`, apiKey);
      if (!data) throw new Error(`Domain ${domain} not found on VirusTotal`);
    
      const attrs = data.data?.attributes ?? {};
      const result: VtDomainResult = {
        domain,
        reputation: attrs.reputation ?? 0,
        analysisStats: attrs.last_analysis_stats ?? { malicious: 0, suspicious: 0, undetected: 0, harmless: 0 },
        categories: attrs.categories ?? {},
        registrar: attrs.registrar,
        creationDate: attrs.creation_date,
        lastAnalysisDate: attrs.last_analysis_date,
        dnsRecords: attrs.last_dns_records?.map((r: any) => ({ type: r.type, value: r.value })),
      };
    
      cache.set(cacheKey, result);
      return result;
    }
  • Tool registration and schema definition for vt_domain.
    const vtDomainTool: ToolDef = {
      name: "vt_domain",
      description: "VirusTotal domain analysis: reputation score, detection stats, categories, registrar, DNS records. Requires VT_API_KEY.",
      schema: {
        domain: z.string().describe("Domain to analyze"),
      },
      execute: async (args, ctx) => {
        const key = requireApiKey(ctx.config.vtApiKey, "VirusTotal", "VT_API_KEY");
        return json(await vtDomain(args.domain as string, key));
      },
    };
  • Result interface definition for the vt_domain tool.
    interface VtDomainResult {
      domain: string;
      reputation: number;
      analysisStats: VtAnalysisStats;
      categories: Record<string, string>;
      registrar?: string;
      creationDate?: number;
      lastAnalysisDate?: number;
      dnsRecords?: { type: string; value: string }[];
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the API key requirement, which is useful context, but doesn't describe rate limits, authentication needs beyond the key, error handling, or what happens if the domain isn't found. For a tool with no annotation coverage, this leaves significant gaps in understanding its operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured in a single sentence that front-loads the core purpose ('VirusTotal domain analysis'), lists key outputs, and ends with the API requirement. There's no wasted text, though it could be slightly more structured (e.g., bullet points for outputs) without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (security analysis with API dependency), no annotations, and no output schema, the description is minimally adequate. It covers the purpose and key outputs but lacks details on behavioral traits, error cases, or return format. For a tool with no structured output documentation, more completeness would be beneficial to guide the agent effectively.

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 the single parameter 'domain' clearly documented as 'Domain to analyze'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 tool's purpose: 'VirusTotal domain analysis' with specific outputs listed (reputation score, detection stats, categories, registrar, DNS records). It distinguishes itself from sibling tools like 'vt_ip' and 'vt_url' by focusing on domain analysis rather than IP or URL analysis. However, it doesn't explicitly contrast with other domain analysis tools like 'whois_domain' or 'st_subdomains'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'Requires VT_API_KEY' and listing analysis outputs, suggesting it's for security/threat intelligence. However, it doesn't explicitly state when to use this tool versus alternatives like 'whois_domain' for registrar info or 'dns_lookup' for DNS records, nor does it mention any exclusions or prerequisites beyond the API key.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/badchars/osint-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server