Mythic MCP

Created By
xpna year ago
A simple POC to expose Mythic as a MCP server
Overview

what is Mythic MCP?

Mythic MCP is a proof of concept (POC) that exposes Mythic as a Managed Control Plane (MCP) server, allowing large language models (LLMs) to perform penetration testing on behalf of users.

how to use Mythic MCP?

To use Mythic MCP, you need to set up the MCP server with Claude Desktop by editing the claude_desktop_config.json file to include the server configuration and then start Claude Desktop.

key features of Mythic MCP?

  • Integration with Claude Desktop for easy deployment
  • Allows LLMs to emulate specific threat actors for pentesting
  • Customizable server configuration for various tasks

use cases of Mythic MCP?

  1. Automating penetration testing tasks using LLMs.
  2. Emulating threat actors to test security measures.
  3. Conducting security assessments in a controlled environment.

FAQ from Mythic MCP?

  • What are the requirements to run Mythic MCP?

You need uv, python3, and Claude Desktop or another MCP client.

  • Can I customize the tasks for the LLM?

Yes! You can provide any task description for the LLM to follow.

  • Is Mythic MCP suitable for production use?

This is a proof of concept and may not be suitable for production environments.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago