PeMCP MCP Server

Arkana - Your entire malware analysis lab, behind one AI prompt. 250+ MCP tools for binary analysis with Claude Code or other MCP

Local serverstdioPython

What is the PeMCP MCP server?

Arkana - Your entire malware analysis lab, behind one AI prompt. 250+ MCP tools for binary analysis with Claude Code or other MCP. The pemcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

From a single prompt, Arkana opens the binary, triages it (CRITICAL -- 43/72 VT detections), extracts the C2 server (cveutb.sa.com), identifies AES-256 encrypted communications via MessagePack, maps 12 MITRE ATT&CK techniques, detects anti-VM checks for VMware/VirtualBox/ Sandboxie, finds the persistence mechanism (Registry Run key), and recovers the operator's PDB path revealing a Vietnamese-speaking threat actor. See the full report.

  • Session continuity — -- Notes, function renames, custom type definitions, and tool history survive context window limits and server restarts, enabling investigations that span hours or days without losing context
  • SOC analysts — -- automated triage with risk scoring, MITRE mapping, and IOC extraction in seconds; web dashboard for visual review
  • Malware reversers — -- natural language drives decompilation, symbolic execution, interactive debugging, and data transforms across multi-stage payloads
  • Incident responders — -- rapid C2 config extraction, network indicators, and structured reports under time pressure
  • Learners — -- built-in interactive RE tutor with Socratic guidance, progress tracking, and hands-on exercises using real tools
  • Threat intel teams — -- automated similarity hashing, family identification, YARA rule generation, and cross-binary function matching

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by JameZUK; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the pemcp mcp server does with a few real requests.

Frequently asked questions

It connects PeMCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with PeMCP directly.