base-mcp-honeypot

dchu3/base-mcp-honeypot

3.1

If you are the rightful owner of base-mcp-honeypot and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

Base honeypot MCP server is designed to simulate vulnerable services to attract and analyze malicious activities.

base-mcp-honeypot

Base honeypot MCP server that wraps the Honeypot.is API.

Configuration

  1. Copy .env.example to .env and fill in the values documented in docs.honeypot.is. Important keys:

    • HONEYPOT_ENABLE_API_KEY — set to true only when you actually need to send an API key. When enabled, provide HONEYPOT_API_KEY and, if required, change HONEYPOT_API_KEY_HEADER (defaults to Authorization, but you can switch to X-API-KEY). Leaving HONEYPOT_ENABLE_API_KEY=false makes every request unauthenticated, mirroring curl -G https://api.honeypot.is/v2/IsHoneypot -d address=….
    • HONEYPOT_SIMULATE_LIQUIDITY / HONEYPOT_FORCE_SIMULATE — defaults for the simulateLiquidity and forceSimulateLiquidity query parameters described under /v2/IsHoneypot.
    • HONEYPOT_MAX_RETRIES and HONEYPOT_RETRY_DELAY_MS — control simple client-side retries for transient DNS/network errors (e.g., EAI_AGAIN).

  2. Install dependencies with npm install (Node.js 20 LTS).

  3. Build and run the server for Codex CLI integrations with:

npm run build
node dist/server.js stdio

Avoid running the MCP server via npm run dev -- stdio inside Codex CLI — the npm banner writes to stdout before the MCP handshake and will cause initialize to fail.