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.19

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.19
File Size Uploaded Provenance Actions
capesolo-0.5.19.tar.gz 7.4 MB Without provenance Details for capesolo-0.5.19.tar.gz

Built distribution (wheel)

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

Total release size: 15.0 MB

Release files / capesolo-0.5.19.tar.gz

Download URL capesolo-0.5.19.tar.gz
Size 7.4 MB
Tags Source
SHA-256 checksum
How to use checksums
739f00fc171696dad0808b4638b94270bb28a7db74e46ea213534478a25cf3cd
BLAKE2b-256 checksum
How to use checksums
5c8b066b37457923914bb62ab590adcc6aeb0d30b2925bf949e91518a907c9df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.11.9

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

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

Security for CAPEsolo 0.5.19

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.19 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