Skip to main content

Python GUI to run capemon in standalone VM. Provides a subset of CAPE (Configuration And Payload Extraction) processing and results.

Quick Start

  • Open an administrator command window.
  • Type capesolo to run.

Alternatively, create a shortcut to CAPEsolo.exe, which will be in the Scripts subdirectory of same location as your python.exe file.

  • Under Advanced, check 'Run as administrator'
  • An icon file is available in the CAPEsolo install folder under site-packages.

Analysis results are found in C:\Users\Public\CAPEsolo\analysis.

  • Can be configured in python-path\site-packages\CAPEsolo\cfg.ini

Revert the VM after each analysis.

MCP Server

  • CAPEsolo includes an MCP server entrypoint for programmatic analysis workflows.
  • Install project dependencies (including mcp) in your environment.

Run

  • Start the server over stdio:
    • CAPEsolo-mcp
    • or python -m CAPEsolo.mcp_server

Available MCP Tools

  • capesolo_analyze_sample
    • Submit a sample for analysis.
    • Key args: sample_path, package (Auto-detect by default), options, timeout, enforce_timeout.
  • capesolo_analyze_password_zip
    • Submit a password-protected ZIP for analysis.
    • Key args: zip_path, optional zip_password (defaults to infected), optional archive_member_path (required when ZIP has multiple files), package, options, timeout, enforce_timeout.
    • ZIP extraction/decryption is handled by SFlock2.
  • capesolo_get_job_status
    • Get job state (queued, running, completed, failed).
  • capesolo_cancel_job
    • Request termination of a running job (same analyzer termination signal used by GUI Kill).
  • capesolo_get_results
    • Return CAPEsolo JSON results using existing keys (target, behavior, signatures, payloads, configs, detections).
  • capesolo_get_job_log_tail
    • Return the last N lines from analysis.log for a job.
  • capesolo_render_html_report
    • Generate an HTML report from completed analysis.
  • capesolo_list_payloads
    • List payload artifacts from analysis output.
  • capesolo_list_dropped_files
    • List dropped files under analysis files output.
  • capesolo_list_debug_logs
    • List debugger and analysis log artifacts.
  • capesolo_update_yara
    • Update CAPE/community YARA rules.

Typical Workflow

  1. Call capesolo_analyze_sample or capesolo_analyze_password_zip.
  2. Poll capesolo_get_job_status until completed.
  3. Call capesolo_get_results (and optionally capesolo_render_html_report).

Headless Single-Run CLI

  • CAPEsolo supports a non-MCP single-run mode that reuses the same backend job runner as the MCP server.
  • Run one analysis and exit:
    • CAPEsolo --headless-analyze "C:\path\sample.exe"
  • Optional flags:
    • --package <name>
    • --options "key=value,key2=value2"
    • --timeout <seconds>
    • --enforce-timeout
    • --headless-json
    • --headless-html-report

MCP Client Config Examples

  • Use these examples to connect CAPEsolo MCP server to common clients.
  • Server command is:
    • CAPEsolo-mcp
    • or python -m CAPEsolo.mcp_server

Claude Desktop

  • Add to Claude Desktop MCP config:
{
  "mcpServers": {
    "capesolo": {
      "command": "python",
      "args": ["-m", "CAPEsolo.mcp_server"],
      "cwd": "C:\\Users\\lkuca\\PycharmProjects\\CAPEsolo"
    }
  }
}

Cursor

  • Add in Cursor MCP servers config:
{
  "mcpServers": {
    "capesolo": {
      "command": "CAPEsolo-mcp",
      "args": []
    }
  }
}

OpenCode

  • Add in OpenCode MCP config:
{
  "mcpServers": {
    "capesolo": {
      "command": "python",
      "args": ["-m", "CAPEsolo.mcp_server"],
      "cwd": "C:\\Users\\lkuca\\PycharmProjects\\CAPEsolo"
    }
  }
}

Codex (Custom Host App)

  • If you run Codex through a custom client/app, configure the app's MCP server map with:
{
  "mcpServers": {
    "capesolo": {
      "command": "CAPEsolo-mcp",
      "args": []
    }
  }
}
  • The host app must support MCP tool calls and pass them through to the Codex model runtime.

PyCharm AI Assistant

  • Open:
    • Settings -> Tools -> AI Assistant -> Model Context Protocol (MCP)
  • Add JSON config:
{
  "mcpServers": {
    "capesolo": {
      "command": "python",
      "args": ["-m", "CAPEsolo.mcp_server"],
      "cwd": "C:\\Users\\lkuca\\PycharmProjects\\CAPEsolo"
    }
  }
}

Quick Connection Test

  1. Start your MCP-enabled client with the config above.
  2. Call capesolo_get_job_status with a fake id:
    • {"job_id":"test"}
  3. Expected response pattern:
    • {"found": false, "error": "Job not found: test"}

Metadata

Release files for CAPEsolo 0.5.22

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for CAPEsolo 0.5.22
File Size Uploaded Provenance Actions
capesolo-0.5.22.tar.gz 7.4 MB Without provenance Details for capesolo-0.5.22.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for CAPEsolo 0.5.22
File Interpreter ABI Platform Actions
capesolo-0.5.22-py3-none-any.whl Python 3 none any Details for capesolo-0.5.22-py3-none-any.whl

Total release size: 15.1 MB

Release files / capesolo-0.5.22.tar.gz

Download URL capesolo-0.5.22.tar.gz
Size 7.4 MB
Tags Source
SHA-256 checksum
How to use checksums
c9202811d92aa14d4a8e4ee67927408b6b8d8322c3c95e8eb1f9dcbbc98fe6c1
BLAKE2b-256 checksum
How to use checksums
56ec091f6955ca8e7ddae1d70b1d85714cc952354c2a5854036637a58ee73688
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.9

Release files / capesolo-0.5.22-py3-none-any.whl

Download URL capesolo-0.5.22-py3-none-any.whl
Size 7.7 MB
Tags Python 3
SHA-256 checksum
How to use checksums
a8d2bc0b69481d5e27e464241804221a121814b7e5d5a1dce354f780f1d4cce6
BLAKE2b-256 checksum
How to use checksums
bd766a575842c6bb990eca09e78606c20fd3fb17bee851df307999b9a187e6c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.9

Security for CAPEsolo 0.5.22

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.5.22 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page