Urlscan Io

Search

search

Read-onlyIdempotent

Search the public urlscan.io archive of website scans using urlscan query syntax, for example page.domain:example.com, task.url, ip, asn, or filename terms, with size and search_after paging and no API key needed. Returns matching scan records with the scanned URL, page domain, IP, ASN, server, scan date, and the scan uuid used to pull the full report. Answers which pages urlscan has already scanned for a domain, brand, or infrastructure indicator.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`size`	No
`query`	Yes
`search_after`	No

Output Schema

TableJSON Schema

Name	Required	Description
`took`	No	Query execution time in milliseconds
`total`	No	Total number of results available
`results`	No	Array of scan results matching the query
`has_more`	No	Whether more results are available

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "phishing"
+  },
+  {
+    "query": "malware",
+    "search_after": "2024-01-15",
+    "size": 50
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results from urlscan.io",
+  "properties": {
+    "has_more": {
+      "description": "Whether more results are available",
+      "type": "boolean"
+    },
+    "results": {
+      "description": "Array of scan results matching the query",
+      "items": {
+        "properties": {
+          "meta": {
+            "description": "Metadata about the scan",
+            "type": "object"
+          },
+          "page": {
+            "description": "Page information from the scan",
+            "type": "object"
+          },
+          "stats": {
+            "description": "Statistics from the scan",
+            "type": "object"
+          },
+          "task": {
+            "description": "Task information for the scan",
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "took": {
+      "description": "Query execution time in milliseconds",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of results available",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds that no API key is required, explains paging via size and search_after, and lists returned fields, which goes beyond annotations. No contradictions.

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 dense sentences with no filler. The core action is front-loaded, and every clause provides useful information, from the archive source to query syntax to return fields.

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?

The description covers query syntax, paging, result contents, authentication (none), and typical use cases. Since an output schema exists and annotations convey safety, no critical information is missing for a read-only search tool.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining the query parameter with concrete syntax examples (page.domain, task.url, etc.) and describing size and search_after as paging controls. All three parameters are effectively documented.

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 uses the specific verb 'Search' and names the resource as 'public urlscan.io archive of website scans', providing query syntax examples. This clearly distinguishes it from sibling tools like domain or ip by focusing on urlscan scan history.

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?

It states the tool 'Answers which pages urlscan has already scanned for a domain, brand, or infrastructure indicator', implying when to use. However, it does not explicitly mention alternatives or exclusions, though the unique archive focus gives strong contextual guidance.

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

All Urlscan Io 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.