# How to connect Virustotal to OpenClaw (paste one key, 16 tools) > Connect Virustotal to OpenClaw with ClawLink: paste your Virustotal key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/virustotal The usual route to Virustotal 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 Virustotal setup: install one ClawHub skill, connect Virustotal in the browser, and OpenClaw can call real Virustotal 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 Virustotal. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Virustotal** — 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 virustotal # connect Virustotal (browser OAuth) npx -y @useclawlink/cli actions virustotal # list available actions npx -y @useclawlink/cli run virustotal --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 Virustotal in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Virustotal API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Virustotal, summarize it in plain English, and point out anything that needs attention. ### 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 Virustotal is connected in the dashboard, that agent calls the same 16 Virustotal 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). ## Virustotal MCP for OpenClaw Looking for a Virustotal MCP server for OpenClaw? ClawLink connects Virustotal to OpenClaw and exposes 16 Virustotal 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 Virustotal integration](https://claw-link.dev/hermes/virustotal) works the same way. ## What the OpenClaw Virustotal integration can do 16 Virustotal tools are ready for OpenClaw once the account is connected. ### All 16 Virustotal tools for OpenClaw | Tool | What it does | |---|---| | **Get analysis** `virustotal_get_analysis` | Retrieve the analysis report of a file or URL submission | | **Get comments** `virustotal_get_comments` | Retrieve the latest comments on a VirusTotal resource | | **Get domain relationships** `virustotal_get_domain_relationships` | Retrieve relationship objects for a given domain | | **Get domain report** `virustotal_get_domain_report` | Retrieve the analysis report of a domain | | **Get file report** `virustotal_get_file_report` | Retrieve the analysis report of a file | | **Get ip address relationships** `virustotal_get_ip_address_relationships` | Retrieve objects related to a specific IP address by relationship type | | **Get ip address report** `virustotal_get_ip_address_report` | Retrieve the analysis report of an IP address | | **Get metadata** `virustotal_get_metadata` | Retrieve VirusTotal metadata | | **Get URL report** `virustotal_get_url_report` | Retrieve the analysis report of a URL | | **Get votes** `virustotal_get_votes` | Retrieve votes on files, URLs, domains, or IP addresses | | **Search** `virustotal_search` | Search for objects in the VirusTotal database | | **Add comment** `virustotal_add_comment` | Add a comment to a VirusTotal resource (file, URL, domain, or IP address) | | **Add vote** `virustotal_add_vote` | Add a vote (harmless/malicious) to a VirusTotal resource | | **Rescan file** `virustotal_rescan_file` | Re-analyze a previously submitted file | | **Scan URL** `virustotal_scan_url` | Submit a URL for scanning | | **Upload file** `virustotal_upload_file` | Upload a file for scanning | ## Example prompts **Get Analysis** > Pull the relevant data from Virustotal, summarize it in plain English, and point out anything that needs attention. **Get Comments** > Pull the relevant data from Virustotal, summarize it in plain English, and point out anything that needs attention. **Get Domain Relationships** > Pull the relevant data from Virustotal, summarize it in plain English, and point out anything that needs attention. **Get Domain Report** > Pull the relevant data from Virustotal, 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 Virustotal working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Virustotal API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Virustotal 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 Virustotal. | 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 Virustotal actions to the runtime in a format your agent can reliably use. | 16 tools for Virustotal are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Virustotal 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 Virustotal in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Virustotal 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 Virustotal skill but can't call the tools The ClawHub skill teaches OpenClaw about Virustotal, but the calls run through the ClawLink plugin and your connected account. Make sure Virustotal 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 Virustotal 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 Virustotal tools Virustotal 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 Virustotal 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. ### Virustotal 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 Virustotal has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Virustotal integration? Yes. ClawLink is the fastest way to connect OpenClaw to Virustotal: link your Virustotal account once in the browser and OpenClaw can call the Virustotal API through 16 ready-made tools — no custom code or token handling. ### How do I add Virustotal to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Virustotal skill from ClawHub, then you click Connect in the dashboard to authorize Virustotal. OpenClaw calls the tools from the next message — no config files, and the Virustotal key you paste is stored server-side instead of in your environment. ### How long does it take to connect Virustotal to OpenClaw? About two minutes. Sign in, click Connect next to Virustotal in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Virustotal 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 Virustotal working from chat. ### OpenClaw installed the Virustotal skill but can't call the tools The ClawHub skill teaches OpenClaw about Virustotal, but the calls run through the ClawLink plugin and your connected account. Make sure Virustotal 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](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.