mcpField
C
cyberwarex-council

cyberwarex-council

Local
cyberwarex.comAI & Agents0Updated 3w ago
RepositoryVisit website

About cyberwarex-council

Second opinion for agents: 3-4 AI models answer, one verdict with confidence and dissent

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cyberwarex-cyberwarex-council": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ],
      "env": {
        "CWX_X_PAYMENT": "<CWX_X_PAYMENT>",
        "CWX_SUBSCRIPTION_KEY": "<CWX_SUBSCRIPTION_KEY>",
        "CWX_COUNCIL_URL": "<CWX_COUNCIL_URL>"
      }
    }
  }
}
Run commanddocker run -i --rm -e CWX_X_PAYMENT -e CWX_SUBSCRIPTION_KEY -e CWX_COUNCIL_URL ghcr.io/cyberwarex/cyberwarex-council:1.1.2
Environment variables to set
CWX_X_PAYMENTSecretOptional x402 X-PAYMENT header. If unset, the server opts into the free trial and then surfaces the 402 invoice to the agent so its own x402 client can pay and retry.
CWX_SUBSCRIPTION_KEYSecretOptional prepaid credit key (cwx_...) from https://safe.cyberwarex.com/subscribe, so no per-call signing is needed.
CWX_COUNCIL_URLOverride the default service URL (https://council.cyberwarex.com).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/cyberwarex/cyberwarex-council:1.1.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.