REMnux MCP Server Logo

REMnux MCP Server

Official

Enables AI assistants to execute malware analysis tools on a REMnux system via Docker, SSH, or local...

9 views
0 installs
Updated Feb 3, 2026
Not audited
Tools I Recommend
Enables AI assistants to execute malware analysis tools on a REMnux system via Docker, SSH, or local connections. It provides automated file-type analysis, structured tool discovery, and security guardrails for streamlined malware investigation.
  1. Click the "Install Now" button in the FastMCP connection interface to open the environment-variable / connection fields.

  2. Generate a strong HTTP bearer token (used by the REMnux MCP server as MCP_TOKEN).

    • Linux / macOS (openssl):
      openssl rand -hex 32
    • Python (any OS with Python):
      python -c "import secrets; print(secrets.token_hex(32))"
    • PowerShell (Windows):
      python -c "import secrets; print(secrets.token_hex(32))"
      Copy the generated hex string (32 bytes => 64 hex chars).
  3. In the FastMCP "Install Now" env list, add the server env:

    • Key: MCP_TOKEN
    • Value: (paste the generated token)
  4. If FastMCP has a place to provide request headers for the client connection, add the HTTP Authorization header so clients will authenticate:

    • Header name: Authorization
    • Header value: Bearer
  5. If you will run the MCP server with CLI flags instead of relying on the env, put the token into the server startup args (FastMCP "args" or command-line field) instead of/in addition to the env:

    • Example flag: --http-token
    • Or set MCP_TOKEN in the env and start without the flag (preferred to avoid exposing token in process listings).
  6. (Optional) If exposing the server on the network, set the host/port values in FastMCP or server args:

    • Example args: --transport=http --http-host=0.0.0.0 --http-port=3000
    • These are CLI flags, not required envs — set them in FastMCP's args/command fields if present.
  7. Save the FastMCP configuration (Install Now) and start the connection/server via FastMCP.

  8. Test the token from the client side (replace HOST:PORT and TOKEN):

    • curl -H "Authorization: Bearer " http://HOST:3000/mcp (verify you get a valid MCP handshake/response)
  9. Secure the token:

    • Store it in a secrets manager or password manager.
    • Rotate it if it is accidentally exposed (generate a new token and update the MCP_TOKEN value in FastMCP).
  10. For SSH or Docker deployment modes (no HTTP transport) you do not need MCP_TOKEN; instead collect these values and enter them in FastMCP fields as needed:

  • Docker container name: run docker ps on the REMnux host to confirm (default: remnux) and place that value in FastMCP container/args.
    - SSH host/user: the REMnux VM IP and user (default user: remnux). Provide SSH password or use SSH agent in FastMCP's connection fields.

Quick Start

View on GitHub

More for Security

View All →

More for Developer Tools

View All →

Similar MCP Servers

A

Adversary MCP Server

A security-focused server that integrates with Cursor IDE to provide real-time vulnerability detection, exploit generation, and security insights during software development.

Security Developer Tools
10
0
Netmex MCP

Netmex MCP

Official

A lightweight and extendable MCP server toolkit that allows developers to build and integrate custom tools with AI assistants through automatic tool discovery from local directories or npm packages.

API Development Developer Tools

Report Issue

Thank you! Your issue report has been submitted successfully.