# How to connect urlscan.io to OpenClaw (paste one key, 50 tools) > Connect urlscan.io to OpenClaw with ClawLink: paste your urlscan.io key once and 50 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/urlscanio The usual route to urlscan.io access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical urlscan.io setup: install one ClawHub skill, connect urlscan.io in the browser, and OpenClaw can call real urlscan.io actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to urlscan.io. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect urlscan.io** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect urlscanio # connect urlscan.io (browser OAuth) npx -y @useclawlink/cli actions urlscanio # list available actions npx -y @useclawlink/cli run urlscanio --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect urlscan.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your urlscan.io API key once. Verify the connection by asking OpenClaw: > Use urlscan.io to download file and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once urlscan.io is connected in the dashboard, that agent calls the same 50 urlscan.io tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## urlscan.io MCP for OpenClaw Looking for a urlscan.io MCP server for OpenClaw? ClawLink connects urlscan.io to OpenClaw and exposes 50 urlscan.io tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes urlscan.io integration](https://claw-link.dev/hermes/urlscanio) works the same way. ## What the OpenClaw urlscan.io integration can do 50 urlscan.io tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 50. ### 30 of 50 urlscan.io tools for OpenClaw | Tool | What it does | |---|---| | **Download file** `urlscanio_download_file` | Retrieve a captured binary file by its SHA-256 hash as a password-encrypted ZIP archive | | **Get account capabilities** `urlscanio_get_account_capabilities` | Get non-sensitive plan, product, feature, visibility, submission, and limit information for the | | **Get brand summary** `urlscanio_get_brand_summary` | Return detectable brands with detected-page totals and latest hits | | **Get channel** `urlscanio_get_channel` | Get one urlscan Pro notification channel by ID while preserving provider-specific metadata and | | **Get data dump link** `urlscanio_get_data_dump_link` | Generate a temporary download URL for a path returned by LIST_DATA_DUMPS | | **Get dom** `urlscanio_get_dom` | Return the plain-text DOM snapshot captured for a completed scan | | **Get hostname history** `urlscanio_get_hostname_history` | Return one page of historical Pro Hostnames observations for a hostname | | **Get incident** `urlscanio_get_incident` | Get one incident's configuration, source, runtime state, and timestamps | | **Get incident states** `urlscanio_get_incident_states` | Retrieve the stored state history for an incident | | **Get live scan resource** `urlscanio_get_live_scan_resource` | Retrieve one temporary result, DOM, screenshot, captured response, or download from the | | **Get quotas** `urlscanio_get_quotas` | Get current products, features, query capabilities, and per-action minute, hour, and day quota | | **Get response content** `urlscanio_get_response_content` | Return textual content captured in a scan response, addressed by its SHA-256 hash | | **Get result** `urlscanio_get_result` | Retrieve the complete metadata and captured request data for a completed scan UUID | | **Get saved search results** `urlscanio_get_saved_search_results` | Run a urlscan Pro saved search and return its current Search API results | | **Get screenshot** `urlscanio_get_screenshot` | Retrieve a completed urlscan.io scan screenshot as a downloadable PNG file reference | | **Get similar results** `urlscanio_get_similar_results` | Find one page of scan results structurally similar to a specified scan | | **Get subscription results** `urlscanio_get_subscription_results` | Resolve a urlscan Pro alert subscription and datasource to its current Search API results | | **List available brands** `urlscanio_list_available_brands` | List brand identifiers and metadata tracked by urlscan.io brand and phishing detection | | **List available countries** `urlscanio_list_available_countries` | List scanner country codes currently accepted by the Scan API | | **List channels** `urlscanio_list_channels` | List email and webhook notification channels for the current user without returning webhook | | **List data dumps** `urlscanio_list_data_dumps` | List available urlscan.io data-dump files for a time window, file type, and date | | **List live scanners** `urlscanio_list_live_scanners` | List Live Scanning nodes available to the connected account and their current metadata | | **List saved searches** `urlscanio_list_saved_searches` | List saved searches owned by or shared with the current user | | **List subscriptions** `urlscanio_list_subscriptions` | List alert subscriptions configured for the current user | | **List user agents** `urlscanio_list_user_agents` | List grouped browser user-agent strings available for scan submission | | **List watchable attributes** `urlscanio_list_watchable_attributes` | List attribute values accepted when configuring incident change monitoring | | **Lookup malicious observable** `urlscanio_lookup_malicious_observable` | Look up malicious-scan occurrence counts and first/last seen timestamps for an IP, hostname | | **Search scans** `urlscanio_search_scans` | Search urlscan.io data with Elasticsearch Query String syntax and return one controllable page | | **Close incident** `urlscanio_close_incident` | Stop ongoing scans for an active urlscan Pro incident and transition it to the closed state | | **Copy incident** `urlscanio_copy_incident` | Create a separate urlscan Pro incident from an existing incident's configuration | ## Example prompts **Download File** > Use urlscan.io to download file and walk me through the result in plain English. **Get Account Capabilities** > Pull the relevant data from urlscan.io, summarize it in plain English, and point out anything that needs attention. **Get Brand Summary** > Pull the relevant data from urlscan.io, summarize it in plain English, and point out anything that needs attention. **Get Channel** > Pull the relevant data from urlscan.io, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want urlscan.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the urlscan.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected urlscan.io account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for urlscan.io. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right urlscan.io actions to the runtime in a format your agent can reliably use. | 50 tools for urlscan.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes urlscan.io to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect urlscan.io in the browser, and the 50 tools above work from chat. There is no SDK and no config file, and the urlscan.io key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the urlscan.io skill but can't call the tools The ClawHub skill teaches OpenClaw about urlscan.io, but the calls run through the ClawLink plugin and your connected account. Make sure urlscan.io is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect urlscan.io from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling urlscan.io tools urlscan.io tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every urlscan.io call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### urlscan.io returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for urlscan.io has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw urlscan.io integration? Yes. ClawLink is the fastest way to connect OpenClaw to urlscan.io: link your urlscan.io account once in the browser and OpenClaw can call the urlscan.io API through 50 ready-made tools — no custom code or token handling. ### How do I add urlscan.io to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink urlscan.io skill from ClawHub, then you click Connect in the dashboard to authorize urlscan.io. OpenClaw calls the tools from the next message — no config files, and the urlscan.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect urlscan.io to OpenClaw? About two minutes. Sign in, click Connect next to urlscan.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring urlscan.io up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want urlscan.io working from chat. ### OpenClaw installed the urlscan.io skill but can't call the tools The ClawHub skill teaches OpenClaw about urlscan.io, but the calls run through the ClawLink plugin and your connected account. Make sure urlscan.io is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.