Qnexus MCP Server

What the code does

We read the source, 6 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

qnexus-mcp похож на nexus-mcp

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add qnexus-mcp -- uvx qnexus-mcp

{
  "mcpServers": {
    "qnexus-mcp": {
      "command": "uvx",
      "args": [
        "qnexus-mcp"
      ]
    }
  }
}

[mcp_servers.qnexus-mcp]
command = "uvx"
args = ["qnexus-mcp"]

{
  "mcpServers": {
    "qnexus-mcp": {
      "command": "uvx",
      "args": [
        "qnexus-mcp"
      ]
    }
  }
}

{
  "servers": {
    "qnexus-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "qnexus-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: QNEXUS_MCP_TOOLSETS (Comma-separated toolsets: read,execute,manage,destructive (default: read)), QNEXUS_MCP_ALLOW_SPEND (Permit credit-spending (HQC) execution (default: false)), QNEXUS_MCP_ALLOW_HARDWARE (Permit real-QPU targets (default: false)), QNEXUS_MCP_ALLOW_DESTRUCTIVE (Permit delete/cancel/archive tools (default: false)), QNEXUS_MCP_MAX_CREDITS (Hard per-call HQC ceiling; 0 blocks all spend (default: 0)), QNEXUS_MCP_MAX_OUTCOMES (Top-N cap on distinct measurement outcomes returned per result item (default: 100)), QNEXUS_MCP_MAX_SUBMISSIONS_PER_MINUTE (Sliding-window submission cap; each circuit in a batch counts as one (default: 6)), QNEXUS_MCP_PROJECTS (Comma-separated project allowlist, enforced on every mutating tool (default: all projects)).