OLETools Secure MCP Server

Created By
pradeep895a year ago
Secure MCP server for analyzing Excel files with oletools
Overview

What is OLETools Secure MCP Server?

OLETools Secure MCP Server is a secure microservice designed to analyze Microsoft Office documents (Excel, Word, PowerPoint) and related file types for potential malicious content using static analysis techniques.

How to use OLETools Secure MCP Server?

To use the server, clone the repository, install the necessary dependencies, configure the Claude Desktop application, and run the server. You can then analyze files by using specific commands in the application.

Key features of OLETools Secure MCP Server?

  • Analyzes VBA Macros and detects XLM Macros.
  • Checks for DDE Links and extracts embedded OLE Objects.
  • Analyzes XLL file exports for suspicious functions.
  • Extracts Indicators of Compromise (IOCs) such as URLs, IPs, and Emails.
  • Provides basic MIME type and file size validation.
  • Configurable scoring system for risk classification.

Use cases of OLETools Secure MCP Server?

  1. Analyzing Excel files for malicious macros.
  2. Detecting suspicious content in Word and PowerPoint documents.
  3. Integrating with systems that support the MCP protocol for enhanced security.

FAQ from OLETools Secure MCP Server?

  • What types of files can be analyzed?

The server can analyze Microsoft Office documents including Excel, Word, and PowerPoint files.

  • Is it necessary to install additional tools?

Yes, you need to install OLETools, XLMMacroDeobfuscator, and other dependencies for full functionality.

  • Can this server be integrated with other applications?

Yes, it is designed for integration with systems that support the MCP protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pradeep895
Star
0
Language
Python
License
-

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