Urlhaus

Get Recent

get_recent

Read-onlyIdempotent

Get a list of recently submitted malware URLs from URLhaus. Useful for monitoring the latest threats.

Input Schema

Name	Required	Description	Default
`limit`	No	Number of recent URLs to return (default 10, max 1000).

Output Schema

Name	Required	Description
`urls`	Yes	List of recently submitted malware URLs
`count`	Yes	Number of recent URLs returned
`query_status`	Yes	Status of the query

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 50
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of recent URLs returned",
+      "type": "number"
+    },
+    "query_status": {
+      "description": "Status of the query",
+      "type": "string"
+    },
+    "urls": {
+      "description": "List of recently submitted malware URLs",
+      "items": {
+        "properties": {
+          "date_added": {
+            "description": "Date when URL was added",
+            "type": "string"
+          },
+          "id": {
+            "description": "URLhaus ID",
+            "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"
+          },
+          "urlhaus_reference": {
+            "description": "Reference URL on URLhaus",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "url",
+          "url_status",
+          "date_added",
+          "threat",
+          "tags",
+          "urlhaus_reference"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query_status",
+    "count",
+    "urls"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "limit": 10,
-    "minmagnitude": 4.5
-  },
-  {
-    "minmagnitude": 2.5
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Total number of earthquakes in response",
-      "type": "number"
-    },
-    "earthquakes": {
-      "description": "List of recent earthquakes",
-      "items": {
-        "properties": {
-          "alert": {
-            "description": "Alert level if applicable",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "depth_km": {
-            "description": "Depth below surface in kilometers",
-            "type": "number"
-          },
-          "id": {
-            "description": "USGS event ID",
-            "type": "string"
-          },
-          "latitude": {
-            "description": "Epicenter latitude",
-            "type": "number"
-          },
-          "longitude": {
-            "description": "Epicenter longitude",
-            "type": "number"
-          },
-          "magnitude": {
-            "description": "Earthquake magnitude",
-            "type": "number"
-          },
-          "place": {
-            "description": "Location description",
-            "type": "string"
-          },
-          "significance": {
-            "description": "Event significance score",
-            "type": "number"
-          },
-          "time": {
-            "description": "Event time in ISO 8601 format",
-            "type": "string"
-          },
-          "tsunami": {
-            "description": "Tsunami warning flag",
-            "type": "boolean"
-          },
-          "type": {
-            "description": "Event type (e.g., earthquake)",
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "magnitude",
-          "place",
-          "time",
-          "latitude",
-          "longitude",
-          "depth_km",
-          "type",
-          "tsunami",
-          "significance"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "earthquakes"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of earthquakes in response",
+      "type": "number"
+    },
+    "earthquakes": {
+      "description": "List of recent earthquakes",
+      "items": {
+        "properties": {
+          "alert": {
+            "description": "Alert level if applicable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "depth_km": {
+            "description": "Depth below surface in kilometers",
+            "type": "number"
+          },
+          "id": {
+            "description": "USGS event ID",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Epicenter latitude",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Epicenter longitude",
+            "type": "number"
+          },
+          "magnitude": {
+            "description": "Earthquake magnitude",
+            "type": "number"
+          },
+          "place": {
+            "description": "Location description",
+            "type": "string"
+          },
+          "significance": {
+            "description": "Event significance score",
+            "type": "number"
+          },
+          "time": {
+            "description": "Event time in ISO 8601 format",
+            "type": "string"
+          },
+          "tsunami": {
+            "description": "Tsunami warning flag",
+            "type": "boolean"
+          },
+          "type": {
+            "description": "Event type (e.g., earthquake)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "magnitude",
+          "place",
+          "time",
+          "latitude",
+          "longitude",
+          "depth_km",
+          "type",
+          "tsunami",
+          "significance"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "earthquakes"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10,
+    "minmagnitude": 4.5
+  },
+  {
+    "minmagnitude": 2.5
+  }
+]

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 readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds that it returns recently submitted malware URLs, which aligns with annotations but does not disclose additional behavioral traits such as rate limits, result ordering, or potential staleness.

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 two sentences: the first states the action clearly, the second provides a use case. There is no redundant or unnecessary wording, and it is efficiently front-loaded.

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?

For a simple tool with one optional parameter, an output schema, and no nested objects, the description covers the core functionality and a typical use case. It could mention the output format explicitly, but the output schema fills that gap.

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?

Input schema has 1 parameter (limit) with a description covering its type, default, and max. Schema description coverage is 100%, so the tool description adds no parameter information beyond what is already in the schema. Baseline score of 3 is appropriate.

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 the tool retrieves recently submitted malware URLs from URLhaus ('Get a list of recently submitted malware URLs from URLhaus'). It names the specific verb and resource, though it does not explicitly differentiate from sibling tools like lookup_url or recent_alerts that may overlap in functionality.

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?

The description implies usage for monitoring latest threats ('Useful for monitoring the latest threats.'), but provides no explicit guidance on when to use this tool versus alternatives, nor any conditions or exclusions.

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.

Get Recent

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources