ClamAV MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_fileC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose that cannot be confused with any other tool in the set.
With only one tool, naming consistency is inherently perfect. The tool name 'scan_file' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool for a ClamAV server feels thin and incomplete. While scanning files is the core function, typical antivirus interfaces would include additional operations like checking database versions, updating signatures, or scanning directories. The scope appears too narrow for practical agent use.
The tool surface is severely incomplete for a ClamAV server. It only provides file scanning, missing essential operations like updating virus definitions, scanning directories, checking service status, or getting scan statistics. This creates significant gaps that will limit agent effectiveness in security workflows.