Filescan.io integration
Filescan.io malware analysis API: submit a file or a link for analysis, follow the resulting scan until every report has finished, read a report with its verdict, extracted indicators and osint findings, search the corpus by filename, file type, verdict, tag, hash or network indicator, list what the account has already uploaded, and read the state and configuration of the service.
Say what should happen.
The workflow builds itself.
Common Filescan.io use cases
- analysing a link reported in a phishing email
- submitting a suspicious attachment for analysis
- checking the maximum file size before submitting a large sample
- reading the report of one file extracted from a submitted archive
- recovering the flow identifier of a submission made by an earlier run
- checking whether a hash has already been analysed before submitting it
- waiting for a submitted file to finish analysing and reading its verdict
- checking whether the service is degraded before blaming a failing submission
- auditing what an automation has submitted for analysis
- explaining why an analysis is taking longer than usual
What you can do with Filescan.io
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Report, 3 operations
get_reportGet reportGETReturns one Filescan.io report for a given report identifier and file hash.get_scan_reportGet scan reportGETPolls a Filescan.io scan and returns its reports once they are finished.search_reportsSearch reportsGETSearches Filescan.io reports by filename, verdict, tag, hash or contacted indicator.
Scan, 2 operations
scan_fileScan filePOSTSubmits a file to Filescan.io and returns the flow identifier to poll.scan_urlScan urlPOSTSubmits a URL to Filescan.io for analysis and returns the flow identifier to poll.
System, 2 operations
get_system_configGet system configGETReturns the Filescan.io service limits and the options a submission may use.get_system_infoGet system infoGETReturns the version and current load of the Filescan.io service.
Upload, 1 operation
list_uploadsList uploadsGETLists the submissions made by the Filescan.io account.
Use Filescan.io from Claude Code, Cursor or Codex
Connect Filescan.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Filescan.io operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Filescan.io
- Create your workspace
Sign up free. Nothing to install.
- Connect Filescan.io once
Add your Filescan.io connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Filescan.io integration FAQ
What can you do with the Filescan.io integration?
LiveContext exposes 8 operations on Filescan.io, covering report, scan, system and upload. Common uses include analysing a link reported in a phishing email, submitting a suspicious attachment for analysis and checking the maximum file size before submitting a large sample.
