Urlhaus

Lookup Payload

lookup_payload

Read-onlyIdempotent

Look up a malware payload file by its MD5 or SHA256 hash in the URLhaus database. Returns file type, size, first/last seen dates, and associated delivery URLs.

Input Schema

Name	Required	Description	Default
`md5_hash`	No	MD5 hash of the payload to look up (32 hex characters).
`sha256_hash`	No	SHA256 hash of the payload to look up (64 hex characters).

Output Schema

Name	Required	Description
`md5_hash`	Yes	MD5 hash of the payload
`file_type`	Yes	File type of the payload
`last_seen`	Yes	Date when payload was last seen
`signature`	Yes	Malware signature name if available
`url_count`	Yes	Number of URLs serving this payload
`first_seen`	Yes	Date when payload was first seen
`sha256_hash`	Yes	SHA256 hash of the payload
`query_status`	Yes	Status of the query
`delivery_urls`	Yes	URLs associated with this payload delivery
`file_size_bytes`	Yes	Size of the payload file in bytes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "delivery_urls": {
+      "description": "URLs associated with this payload delivery",
+      "type": "array"
+    },
+    "file_size_bytes": {
+      "description": "Size of the payload file in bytes",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "file_type": {
+      "description": "File type of the payload",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "first_seen": {
+      "description": "Date when payload was first seen",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_seen": {
+      "description": "Date when payload was last seen",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "md5_hash": {
+      "description": "MD5 hash of the payload",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query_status": {
+      "description": "Status of the query",
+      "type": "string"
+    },
+    "sha256_hash": {
+      "description": "SHA256 hash of the payload",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "signature": {
+      "description": "Malware signature name if available",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url_count": {
+      "description": "Number of URLs serving this payload",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "query_status",
+    "md5_hash",
+    "sha256_hash",
+    "file_type",
+    "file_size_bytes",
+    "signature",
+    "first_seen",
+    "last_seen",
+    "url_count",
+    "delivery_urls"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "md5_hash": "d41d8cd98f00b204e9800998ecf8427e"
+  },
+  {
+    "sha256_hash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+  }
+]

First observedApr 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description isn't needed for safety. It adds context about the data source (URLhaus) and output fields but doesn't disclose any additional behavioral traits (e.g., rate limits, authentication). This is adequate but not exceptional.

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?

The description is a single, front-loaded sentence that efficiently conveys purpose and results. It is concise without being overly terse, though it could be slightly more structured (e.g., separate result list).

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?

With an output schema present (even if not shown here), the description sufficiently covers inputs and outputs. It mentions the database and key return fields. It lacks details like number of results or authentication, but for a lookup tool with good annotations, this is nearly complete.

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% and each parameter has a clear description (hash format and length). The tool description does not add extra meaning beyond that, so it meets the baseline but doesn't exceed.

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 action: look up a malware payload by MD5 or SHA256 hash. It specifies the database (URLhaus) and lists the returned fields, distinguishing it from sibling tools like lookup_host and lookup_url.

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?

The description implies when to use the tool (when you have a hash and need payload info). It doesn't explicitly state exclusions or alternatives, but the sibling context makes differentiation clear. Adding a note that at least one hash is required would improve it.

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.