Skip to main content
Glama
Sentinel-One

Purple AI MCP Server

Official
by Sentinel-One

threat_intel_by_ip

Retrieve threat intelligence for an IP address from VirusTotal, including reputation scores, geolocation, and network ownership for investigating suspicious activity.

Instructions

Get threat intelligence for an IP address from VirusTotal/Google Threat Intelligence.

This tool queries VirusTotal's database to retrieve comprehensive threat intelligence about an IP address, including reputation, geolocation, ASN data, and relationships.

What this tool provides:

  • IP reputation and detection status from 90+ security vendors

  • Geolocation data (country, city, coordinates)

  • ASN (Autonomous System Number) and network owner

  • Associated files, URLs, and domains

  • Passive DNS data

  • Historical analysis results

  • Open ports and services (if available)

  • Threat categories and tags

  • Community reputation scores

Common Use Cases:

  • Investigate suspicious IPs from firewall logs

  • Research malware C2 servers

  • Validate IP reputation before allowing connections

  • Identify attacker infrastructure in incident response

  • Threat hunting for known malicious IPs

  • Network forensics and attribution

Args: ip_address: The IP address to query (IPv4 or IPv6).

Returns: JSON string containing comprehensive threat intelligence data including: - Detection statistics from security vendors - Geolocation and network information - ASN and owner details - Related malware, domains, and URLs - Reputation score and categories - Historical connection data

Examples: "8.8.8.8" "192.168.1.1" "2001:4860:4860::8888"

Notes: - Requires a valid VirusTotal API key (PURPLEMCP_VT_API_KEY environment variable) - Results include historical data aggregated over time - Private/internal IPs may have limited or no data - Private API keys have higher rate limits - When an IP 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
ip_addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided; description covers key behaviors: requires API key, returns historical data, private IPs may lack data, structured JSON for missing IPs, and error types. Does not mention mutation/read nature explicitly but implied.

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

Conciseness3/5

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

Well-structured with sections, but verbose with many bullet points. Some redundancy (e.g., reputation mentioned twice). Front-loads purpose effectively but could be trimmed.

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 the simple input (1 parameter) and existence of output schema, the description is very thorough: covers input, output fields, notes, errors, and examples. No gaps identified.

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

Parameters4/5

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

The one parameter (ip_address) is described clearly with type and examples (IPv4/IPv6), compensating for 0% schema description coverage. The description adds context beyond the schema's property definition.

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 that the tool retrieves threat intelligence for an IP address from VirusTotal/GTI. It lists features and use cases, but does not explicitly differentiate from sibling tools like threat_intel_by_domain or threat_intel_by_hash.

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?

Provides explicit use cases (e.g., investigate suspicious IPs, research C2 servers) and notes on limitations (private IPs, API key requirements). However, no guidance on when not to use or alternatives among sibling threat intel tools.

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