Skip to main content
Glama
Sign In

Urlhaus

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Lookup Host

lookup_host
Read-onlyIdempotent

Look up a hostname or IP address in the URLhaus database to find associated malware URLs. Returns all known malicious URLs hosted on that host.

Input Schema

NameRequiredDescriptionDefault
hostYesHostname or IP address to look up (e.g. "example.com" or "192.168.1.1").

Output Schema

NameRequiredDescriptionDefault
urlsYesList of malware URLs on this host
url_countYesNumber of malware URLs found on this host
blacklistsYesBlacklist detection status by various services
query_statusYesStatus of the query
urlhaus_referenceYesReference URL on URLhaus for this host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "blacklists": {
+      "description": "Blacklist detection status by various services",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "query_status": {
+      "description": "Status of the query",
+      "type": "string"
+    },
+    "url_count": {
+      "description": "Number of malware URLs found on this host",
+      "type": "number"
+    },
+    "urlhaus_reference": {
+      "description": "Reference URL on URLhaus for this host",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "urls": {
+      "description": "List of malware URLs on this host",
+      "items": {
+        "properties": {
+          "date_added": {
+            "description": "Date when URL was added",
+            "type": "string"
+          },
+          "id": {
+            "description": "URLhaus ID for this URL",
+            "type": "string"
+          },
+          "tags": {
+            "description": "Associated tags",
+            "items": {
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "threat": {
+            "description": "Threat category",
+            "type": "string"
+          },
+          "url": {
+            "description": "The malware URL",
+            "type": "string"
+          },
+          "url_status": {
+            "description": "Status of the URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "url",
+          "url_status",
+          "date_added",
+          "threat",
+          "tags"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query_status",
+    "urlhaus_reference",
+    "blacklists",
+    "url_count",
+    "urls"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "host": "malicious-site.com"
+  },
+  {
+    "host": "192.168.1.100"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds context about the data source (URLhaus) and explicitly states it returns all known malicious URLs. No contradiction.

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?

Two sentences, front-loaded with purpose, no extraneous information. Every sentence adds value.

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?

Simple one-parameter lookup tool with output schema explaining return values. Description covers all necessary context: data source, input, output.

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 coverage is 100% with clear description and example. Description adds no further semantics beyond what the schema already provides.

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 verb 'look up', resource 'hostname or IP address in URLhaus database', and output 'malicious URLs'. Distinguishes from sibling lookup_payload and lookup_url by specifying host lookup.

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?

Context implies usage when you have a host/IP and want associated malware URLs, but no explicit when to use vs alternatives or when not to use. Sibling tools exist for different lookup types, but the description does not guide selection.

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

All Urlhaus toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources