ClamAV MCP

Created By
a2amarketa year ago
ClamAV MCP Server to scan files for viruses
Overview

what is ClamAV MCP?

ClamAV MCP is a server application that utilizes the ClamAV engine to scan files for viruses, providing a simple interface for file scanning.

how to use ClamAV MCP?

To use ClamAV MCP, ensure ClamAV is installed on your system, then run the MCP server using the command uv run main.py. You can then send files to be scanned via the provided API endpoint.

key features of ClamAV MCP?

  • Utilizes the ClamAV engine for virus scanning
  • Simple API for file scanning
  • Supports multiple operating systems (Ubuntu, Windows, macOS)

use cases of ClamAV MCP?

  1. Scanning files for viruses before uploading to a server.
  2. Integrating virus scanning into applications that handle file uploads.
  3. Regularly scanning files on a system for security compliance.

FAQ from ClamAV MCP?

  • What is required to run ClamAV MCP?

You need to have ClamAV installed on your system.

  • How do I install ClamAV?

Installation instructions are provided for Ubuntu, Windows, and macOS in the documentation.

  • What is the API endpoint for scanning files?

The API provides a scan_file endpoint that accepts base64 encoded file data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
a2amarket
Star
1
Language
Python
License
Apache-2.0 license
Category
security
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago