Urlhaus

Lookup Url

lookup_url

Read-onlyIdempotent

Look up a URL in the URLhaus malware database to check if it is known to host or distribute malware. Returns threat category, status, blacklist status, and tags.

Input Schema

Name	Required	Description	Default
`url`	Yes	The full URL to look up (e.g. "http://example.com/malware.exe").

Output Schema

Name	Required	Description
`id`	Yes	URLhaus ID for this URL
`tags`	Yes	Associated tags for the URL
`threat`	Yes	Threat category (e.g. 'malware', 'phishing')
`blacklists`	Yes	Blacklist detection status by various services
`date_added`	Yes	Date when URL was added to database
`url_status`	Yes	Status of the URL (e.g. 'online', 'offline')
`query_status`	Yes	Status of the query (e.g. 'ok', 'no_results')

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "url": "http://malicious-site.com/payload.exe"
+  },
+  {
+    "url": "https://phishing-domain.net/fake-login.html"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "blacklists": {
+      "description": "Blacklist detection status by various services",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "date_added": {
+      "description": "Date when URL was added to database",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "URLhaus ID for this URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query_status": {
+      "description": "Status of the query (e.g. 'ok', 'no_results')",
+      "type": "string"
+    },
+    "tags": {
+      "description": "Associated tags for the URL",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "threat": {
+      "description": "Threat category (e.g. 'malware', 'phishing')",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url_status": {
+      "description": "Status of the URL (e.g. 'online', 'offline')",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "query_status",
+    "id",
+    "url_status",
+    "date_added",
+    "threat",
+    "tags",
+    "blacklists"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 11, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "url": "http://malicious-site.com/payload.exe"
-  },
-  {
-    "url": "https://phishing-domain.net/fake-login.html"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "blacklists": {
-      "description": "Blacklist detection status by various services",
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "date_added": {
-      "description": "Date when URL was added to database",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "description": "URLhaus ID for this URL",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "query_status": {
-      "description": "Status of the query (e.g. 'ok', 'no_results')",
-      "type": "string"
-    },
-    "tags": {
-      "description": "Associated tags for the URL",
-      "items": {
-        "type": "string"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "threat": {
-      "description": "Threat category (e.g. 'malware', 'phishing')",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url_status": {
-      "description": "Status of the URL (e.g. 'online', 'offline')",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "query_status",
-    "id",
-    "url_status",
-    "date_added",
-    "threat",
-    "tags",
-    "blacklists"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "blacklists": {
+      "description": "Blacklist detection status by various services",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "date_added": {
+      "description": "Date when URL was added to database",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "URLhaus ID for this URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query_status": {
+      "description": "Status of the query (e.g. 'ok', 'no_results')",
+      "type": "string"
+    },
+    "tags": {
+      "description": "Associated tags for the URL",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "threat": {
+      "description": "Threat category (e.g. 'malware', 'phishing')",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url_status": {
+      "description": "Status of the URL (e.g. 'online', 'offline')",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "query_status",
+    "id",
+    "url_status",
+    "date_added",
+    "threat",
+    "tags",
+    "blacklists"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "url": "http://malicious-site.com/payload.exe"
+  },
+  {
+    "url": "https://phishing-domain.net/fake-login.html"
+  }
+]

First observedApr 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds that it queries an external database (URLhaus) and returns specific fields. However, it does not disclose potential rate limits, authentication requirements, or behavior on non-malicious URLs. The description provides some additional context but is not exhaustive.

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 concise and well-structured: two sentences, the first stating the action and purpose, the second listing return fields. No unnecessary details, and each sentence serves a clear function.

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

Completeness4/5

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

Given the tool's simplicity (one parameter, annotations indicating safe operation, and an output schema), the description covers the essential aspects. It explains the purpose, the data source, and return values. It could mention limitations or typical use cases, but overall it is adequate for an AI agent to understand and invoke the tool correctly.

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% coverage for its single parameter 'url', with a clear description and examples. The description does not add extra meaning beyond confirming the parameter is a URL and mentioning the database context. Since the schema already covers the parameter thoroughly, the description adds minimal value here.

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?

The description clearly states the tool's purpose: to look up a URL in the URLhaus database to check for malware. It specifies the database (URLhaus) and the return fields (threat category, status, blacklist status, tags). This distinguishes it from sibling tools like lookup_host or lookup_payload, which target different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool versus alternatives like lookup_host or lookup_payload. It only states what it does, leaving the agent to infer usage context. No explicit exclusions or comparisons are given, which is a gap given the sibling tools.

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

All Urlhaus tools Inspect

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.

Lookup Url

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources