Cybersim Pro

io.github.kayembahamidPublished by GitHub account kayembahamidv1.0.1Updated Oct 24, 2026

Cybersecurity training, simulation, and incident response MCP server

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server for cybersecurity training, simulation, and incident response exercises.

What you can do
Cybersim Pro is described as a cybersecurity training, simulation, and incident response MCP server. It runs as a local process on the user's machine and is meant to support security exercises and response workflows through an AI assistant. No tool list is published, so the exact capabilities are not documented in the available material.
When to use it
Consider it when you want an assistant to help with cybersecurity training scenarios, simulations, or incident response practice. Because no tools are listed, verify the actual capabilities before relying on it for real response work.
Requirements
Runs locally over stdio, distributed as a Docker image (docker.io/hamcodes/cybersim-pro-mcp:v1.0.1), so Docker is needed. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Before you install
No tools, permissions, or data handling are documented, so it is unclear what the server can read, change, or delete on your machine. Review the image and its behavior before running it, especially in any environment holding sensitive data.

Installation

In SourceWeft

  1. Open Cybersim Pro in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.