Mythic_mcp

Name: Mythic_mcp
Author: xpn

by xpn

A simple POC to expose Mythic as a MCP server

74 0 tools GitHub

No known CVEs

No license

Stale

Last commit 436d ago

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

Security

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mythic_mcp": {
      "args": [
        "--directory",
        "/full/path/to/mythic_mcp/",
        "run",
        "main.py",
        "mythic_admin",
        "mythic_admin_password",
        "localhost",
        "7443"
      ],
      "command": "/Users/xpn/.local/bin/uv"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/mythic-mcp)](https://mcppedia.org/s/mythic-mcp)

Read me

What Mythic_mcp does

A quick MCP demo for Mythic, allowing LLMs to pentest on our behalf!

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

25/100across 5 weighted dimensions

How we score →

0255075100

−75

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Mythic_mcp safe to use?: Mythic_mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install Mythic_mcp?: Mythic_mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with Mythic_mcp?: Mythic_mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is Mythic_mcp actively maintained?: Mythic_mcp is not actively maintained — last commit was 436 days ago. It has 74 GitHub stars.

Similar servers

Others in security

View all →

Evil Mcp Server93

An evil MCP server used for redteam testing

30 1

io.github.jasonxkensei/xproof92

Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.

1 1

Ida Pro Mcp92

AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.

9.0k 3

Mcpki Server92

mcpki-server is the backend infrastructure for https://www.mcpki.org, enabling secure public key management and autonomous certificate handling for large language models (LLMs).

MCP Security Weekly

Get CVE alerts and security updates for Mythic_mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

{ "mcpServers": { "mythic_mcp": { "args": [ "--directory", "/full/path/to/mythic_mcp/", "run", "main.py", "mythic_admin", "mythic_admin_password", "localhost", "7443" ], "command": "/Users/xpn/.local/bin/uv" } } }

Usage with Claude Desktop

To deploy this MCP Server with Claude Desktop, you'll need to edit your claude_desktop_config.json to add the following:

{ "mcpServers": { "mythic_mcp": { "command": "/Users/xpn/.local/bin/uv", "args": [ "--directory", "/full/path/to/mythic_mcp/", "run", "main.py", "mythic_admin", "mythic_admin_password", "localhost", "7443" ] } } }

Once done, kick off Claude Desktop. There are sample prompts to show how to task the LLM, but really anything will work along the lines of:

You are an automated pentester, tasked with emulating a specific threat actor. The threat actor is APT31. Your objective is: Add a flag to C:\win.txt on DC01. Perform any required steps to meet the objective, using only techniques documented by the threat actor.

Frequently Asked Questions

Is Mythic_mcp safe to use?

Mythic_mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install Mythic_mcp?

Mythic_mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with Mythic_mcp?

Mythic_mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is Mythic_mcp actively maintained?

Mythic_mcp is not actively maintained — last commit was 436 days ago. It has 74 GitHub stars.

Mythic MCP

A quick MCP demo for Mythic, allowing LLMs to pentest on our behalf!

Requirements

uv
python3
Claude Desktop (or other MCP Client)

Usage with Claude Desktop

To deploy this MCP Server with Claude Desktop, you'll need to edit your claude_desktop_config.json to add the following:

{
    "mcpServers": {
        "mythic_mcp": {
            "command": "/Users/xpn/.local/bin/uv",
            "args": [
                "--directory",
                "/full/path/to/mythic_mcp/",
                "run",
                "main.py",
                "mythic_admin",
                "mythic_admin_password",
                "localhost",
                "7443"
            ]
        }
    }
}

Once done, kick off Claude Desktop. There are sample prompts to show how to task the LLM, but really anything will work along the lines of:

You are an automated pentester, tasked with emulating a specific threat actor. The threat actor is APT31. Your objective is: Add a flag to C:\win.txt on DC01. Perform any required steps to meet the objective, using only techniques documented by the threat actor.