Skip to main content
Glama
badchars

osint-mcp-server

by badchars

vt_url

Scan URLs with VirusTotal to detect malicious, suspicious, or harmless content through comprehensive security analysis.

Instructions

Submit a URL to VirusTotal for scanning and get analysis results (malicious/suspicious/harmless). Requires VT_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to scan

Implementation Reference

  • Implementation of the vtUrl function which submits a URL to VirusTotal for analysis and attempts to fetch the analysis results.
    export async function vtUrl(url: string, apiKey: string): Promise<VtUrlResult> {
      // Submit URL for analysis
      await limiter.acquire();
      const submitRes = await fetch(`${VT_BASE}/urls`, {
        method: "POST",
        headers: { "x-apikey": apiKey, "Content-Type": "application/x-www-form-urlencoded" },
        body: `url=${encodeURIComponent(url)}`,
      });
    
      if (!submitRes.ok) throw new Error(`VirusTotal URL submit failed: ${submitRes.status}`);
      const submitData = await submitRes.json();
      const analysisId = submitData.data?.id;
    
      if (!analysisId) {
        return { url, status: "submitted", analysisId: undefined };
      }
    
      // Try to get analysis results (may not be ready yet)
      try {
        const analysisData = await vtFetch(`/analyses/${analysisId}`, apiKey);
        if (analysisData?.data?.attributes?.status === "completed") {
          return {
            url,
            analysisId,
            analysisStats: analysisData.data.attributes.stats,
            status: "completed",
          };
        }
        return { url, analysisId, status: analysisData?.data?.attributes?.status ?? "queued" };
      } catch {
        return { url, analysisId, status: "queued" };
      }
    }
  • TypeScript interface defining the result structure for vtUrl analysis.
    interface VtUrlResult {
      url: string;
      analysisId?: string;
      analysisStats?: VtAnalysisStats;
      status: string;
    }
  • Registration of the vt_url tool, defining its metadata and the execution logic calling vtUrl.
    const vtUrlTool: ToolDef = {
      name: "vt_url",
      description: "Submit a URL to VirusTotal for scanning and get analysis results (malicious/suspicious/harmless). Requires VT_API_KEY.",
      schema: {
        url: z.string().describe("URL to scan"),
      },
      execute: async (args, ctx) => {
        const key = requireApiKey(ctx.config.vtApiKey, "VirusTotal", "VT_API_KEY");
        return json(await vtUrl(args.url as string, key));
      },
    };
Behavior2/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 mentions the API key requirement, which is useful, but doesn't disclose other behavioral traits such as rate limits, authentication needs beyond the key, whether it's a read-only or destructive operation, or what the response format looks like. This leaves significant gaps for a tool that interacts with an external service.

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 and concise, consisting of two sentences that efficiently convey the tool's purpose and a key requirement. Every sentence adds value without unnecessary details, making it easy to understand quickly.

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

Completeness2/5

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

Given the complexity of interacting with VirusTotal (an external API), no annotations, and no output schema, the description is incomplete. It lacks information on behavioral aspects like rate limits, error handling, or the structure of analysis results, which are crucial for effective tool use. The API key mention is helpful but insufficient for full context.

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?

The input schema has 100% description coverage, with the 'url' parameter documented as 'URL to scan.' The description doesn't add any additional meaning beyond this, such as format constraints or examples. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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: 'Submit a URL to VirusTotal for scanning and get analysis results (malicious/suspicious/harmless).' It specifies the verb ('submit'), resource ('URL'), and outcome ('analysis results'), but doesn't explicitly differentiate it from sibling tools like 'vt_domain' or 'vt_ip' that also submit different resources to VirusTotal.

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 by mentioning 'Requires VT_API_KEY,' which suggests a prerequisite, but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'vt_domain' or 'vt_ip' for different types of inputs. The context is clear but lacks sibling differentiation.

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