Skip to main content
Glama
badchars

osint-mcp-server

by badchars

vt_ip

Analyze IP addresses for security threats using VirusTotal data, providing reputation scores, detection statistics, and network information to identify potential risks.

Instructions

VirusTotal IP analysis: reputation, detection stats, country, ASN, network. Requires VT_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesIP address to analyze

Implementation Reference

  • Implementation of the VirusTotal IP analysis logic.
    export async function vtIp(ip: string, apiKey: string): Promise<VtIpResult> {
      const cacheKey = `vt:ip:${ip}`;
      const cached = cache.get(cacheKey);
      if (cached) return cached;
    
      const data = await vtFetch(`/ip_addresses/${encodeURIComponent(ip)}`, apiKey);
      if (!data) throw new Error(`IP ${ip} not found on VirusTotal`);
    
      const attrs = data.data?.attributes ?? {};
      const result: VtIpResult = {
        ip,
        reputation: attrs.reputation ?? 0,
        analysisStats: attrs.last_analysis_stats ?? { malicious: 0, suspicious: 0, undetected: 0, harmless: 0 },
        country: attrs.country,
        asn: attrs.asn,
        asOwner: attrs.as_owner,
        network: attrs.network,
      };
    
      cache.set(cacheKey, result);
      return result;
    }
  • Result interface for VtIp.
    interface VtIpResult {
      ip: string;
      reputation: number;
      analysisStats: VtAnalysisStats;
      country?: string;
      asn?: number;
      asOwner?: string;
      network?: string;
    }
  • Registration of the vt_ip tool within the protocol handler registry.
    const vtIpTool: ToolDef = {
      name: "vt_ip",
      description: "VirusTotal IP analysis: reputation, detection stats, country, ASN, network. Requires VT_API_KEY.",
      schema: {
        ip: z.string().describe("IP address to analyze"),
      },
      execute: async (args, ctx) => {
        const key = requireApiKey(ctx.config.vtApiKey, "VirusTotal", "VT_API_KEY");
        return json(await vtIp(args.ip as string, key));
      },
    };
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds value by disclosing the API key requirement (auth needs) and listing analysis outputs, but lacks details on rate limits, error handling, or response format. This is a minimal but adequate disclosure for a read-only tool.

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 extremely concise and front-loaded, packing essential information into one sentence: purpose, key data points, and prerequisite. Every word earns its place with zero waste.

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 (single parameter, no output schema, no annotations), the description is complete enough for basic use but lacks depth. It covers purpose and auth needs but omits behavioral details like rate limits or output structure, which could be helpful for an agent.

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 parameter 'ip' clearly documented. The description doesn't add meaning beyond the schema (e.g., no format examples or constraints), so it meets the baseline of 3 where the schema does the heavy lifting.

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 IP analysis' with specific data points (reputation, detection stats, country, ASN, network). It distinguishes from siblings like vt_domain and vt_url by specifying IP analysis, though it doesn't explicitly contrast with all OSINT tools in the list.

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 mentioning 'Requires VT_API_KEY' and specifying IP analysis, suggesting it's for VirusTotal data on IPs. However, it doesn't explicitly state when to use this versus alternatives like shodan_host, geoip_lookup, or other vt_* tools, leaving some ambiguity.

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