Skip to main content
Glama
Sentinel-One

Purple AI MCP Server

Official
by Sentinel-One

threat_intel_by_domain

Query VirusTotal for domain threat intelligence including reputation, WHOIS, DNS, and detection results from 90+ security vendors. Investigate suspicious domains in incident response.

Instructions

Get threat intelligence for a domain from VirusTotal/Google Threat Intelligence.

This tool queries VirusTotal's database to retrieve comprehensive threat intelligence about a domain name, including reputation, detection results, WHOIS data, and relationships.

What this tool provides:

  • Domain reputation and detection status from 90+ security vendors

  • WHOIS registration information

  • DNS resolution history

  • Associated files, URLs, and IP addresses

  • SSL certificates

  • Subdomains discovered

  • Threat categories (malware, phishing, etc.)

  • Historical analysis data

  • Community reputation scores

Common Use Cases:

  • Investigate suspicious domains from email headers or logs

  • Research command & control infrastructure

  • Validate domain reputation before allowing access

  • Identify malicious infrastructure in incident response

  • Threat hunting for known bad actor domains

Args: domain: The domain name to query (e.g., "example.com").

Returns: JSON string containing comprehensive threat intelligence data including: - Detection statistics from security vendors - WHOIS registration details - DNS records and resolution history - Related malware, IPs, and URLs - Reputation score and categories - SSL certificate information

Examples: "google.com" "malicious-c2.example.com" "phishing-site.test"

Notes: - Requires a valid VirusTotal API key (PURPLEMCP_VT_API_KEY environment variable) - Results include historical data aggregated over time - Private API keys have higher rate limits - When a domain is not found, returns a structured JSON response with found=false

Raises: ThreatIntelligenceClientError: If there's an error communicating with the API. RuntimeError: If the API key is not configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Details API key requirement, rate limit differences, error raises, and response format for not-found. Discloses read-only nature implicitly.

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?

Well-structured with sections (What, Use Cases, Args, Returns, Examples, Notes, Raises), but slightly verbose with redundancy (e.g., repetition of domain intelligence details). Still earns its place.

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?

Given single parameter and existence of output schema, description covers purpose, usage, behavioral nuances, parameter details, examples, prerequisites, and error handling. Complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter 'domain'. Schema description coverage is 0%, but description provides clear definition with example format and additional examples section, fully compensating.

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?

Description clearly states 'Get threat intelligence for a domain' with specific verb and resource. Differentiates from sibling threat intel tools (by hash, IP, URL) by specifying domain focus.

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?

Lists common use cases (investigate domains, research C2, etc.) and notes outcomes like 'not found returns structured JSON'. Lacks explicit when-not-to-use or direct comparison to alternatives, but context is clear.

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/Sentinel-One/purple-mcp'

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