# io.github.cyberwareX/cyberwarex-council (oci · ghcr.io/cyberwarex/cyberwarex-council)

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

- Trust score: 49/100 (low)
- Change this week: −3
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **Deprecated**: this server is marked deprecated in the MCP registry. The registry records this reason: "Retired 2026-11-04: the Agent Council service is shut down. See `https://cyberwarex.com` for live CyberWareX tools."

## Components

- oci · `ghcr.io/cyberwarex/cyberwarex-council`: 49/100 (this document), [markdown](https://verifymcp.io/servers/cyberwarex-cyberwarex-council/ghcr-io-cyberwarex-cyberwarex-council.md), [page](https://verifymcp.io/servers/cyberwarex-cyberwarex-council/ghcr-io-cyberwarex-cyberwarex-council)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cyberwarex/cyberwarex-council`
- Version: `1.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 36 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 472 tokens (~157/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.cyberwareX/cyberwarex-council MCP server?

io.github.cyberwareX/cyberwarex-council runs locally as a container image, launched with docker run --rm -i -e CWX_X_PAYMENT -e CWX_SUBSCRIPTION_KEY -e CWX_COUNCIL_URL ghcr.io/cyberwarex/cyberwarex-council:1.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cyberwarex-cyberwarex-council -- docker run --rm -i -e CWX_X_PAYMENT -e CWX_SUBSCRIPTION_KEY -e CWX_COUNCIL_URL ghcr.io/cyberwarex/cyberwarex-council:1.1.2
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "cyberwarex-cyberwarex-council": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ]
    }
  }
}
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "cyberwarex-cyberwarex-council": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ]
    }
  }
}
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add cyberwarex-cyberwarex-council -- docker run --rm -i -e CWX_X_PAYMENT -e CWX_SUBSCRIPTION_KEY -e CWX_COUNCIL_URL ghcr.io/cyberwarex/cyberwarex-council:1.1.2
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyberwarex-cyberwarex-council": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ],
      "enabled": true
    }
  }
}
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  cyberwarex-cyberwarex-council:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "CWX_X_PAYMENT", "-e", "CWX_SUBSCRIPTION_KEY", "-e", "CWX_COUNCIL_URL", "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"]
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "cyberwarex-cyberwarex-council": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ]
    }
  }
}
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "cyberwarex-cyberwarex-council": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ]
    }
  }
}
```

This image reads CWX_X_PAYMENT, CWX_SUBSCRIPTION_KEY and CWX_COUNCIL_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 49, −3)

- [functional] Stability: pass → 0.73

### 2026-10-29 (score 52, 0)

- [security] Stability: 0.97 → pass

### 2026-10-28 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `council` (~161 tokens)

Get a second opinion from 3 DIFFERENT AI models before acting on a judgement call. Each model answers your question independently, then a chair returns one verdict with a confidence score, the points every model agreed on, the dissent, and what would change the answer. Use it when the next step depends on an opinion rather than a fact: is this safe, is it worth it, which option. Gate an irreversible action on `confidence` and `dissent` rather than on one model's certainty. Costs $0.01 in USDC per call over x402, no account.

Input parameters:

- `question` (string, required): The question to put to the council. A decision question works best: include the options and the constraints you are weighing, in one or two sentences.

### `council_deep` (~127 tokens)

The same panel with 4 models and two rounds: every seat sees the other seats' positions and revises, so you get a verdict that survived cross-examination plus each seat's changed_after_debate flag and strongest objection. Use it when being wrong is expensive, or when a `council` call came back with low confidence or real dissent. $0.03 in USDC per call.

Input parameters:

- `question` (string, required): The question to put to the council. A decision question works best: include the options and the constraints you are weighing, in one or two sentences.

### `council_grounded` (~184 tokens)

Deliberation on bought FACTS rather than on model recollection. Your question is scanned for a contract address, a URL or a $TICKER; the matching evidence is purchased (honeypot and owner-powers simulation, OFAC sanctions screen, the actual page content, SEC company profile, open web results), handed to 4 different models, and argued over two rounds. The response lists every source consulted and exactly what was spent on your behalf. Use it before accepting an unknown token, counterparty, link or ticker. Priced per question, $0.05 to $0.12 in USDC: call it unpaid first to get the itemised quote for free.

Input parameters:

- `question` (string, required): The question to put to the council. A decision question works best: include the options and the constraints you are weighing, in one or two sentences.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cyberwarex-cyberwarex-council/ghcr-io-cyberwarex-cyberwarex-council#diagnostics

## Score history

- 2026-11-05: 49
- 2026-11-04: 49
- 2026-11-03: 52
- 2026-11-02: 52
- 2026-11-01: 52
- 2026-10-31: 52
- 2026-10-30: 52
- 2026-10-29: 52
- 2026-10-28: 52
- 2026-10-27: 51
- 2026-10-26: 51
- 2026-10-25: 51
- 2026-10-24: 50
- 2026-10-23: 50
- 2026-10-22: 49
- 2026-10-21: 49
- 2026-10-20: 48
- 2026-10-19: 48
- 2026-10-18: 47
- 2026-10-17: 47
- 2026-10-16: 46
- 2026-10-15: 46
- 2026-10-14: 45
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-10: 38
- 2026-10-07: 38
- 2026-10-04: 38
- 2026-10-03: 38
- 2026-10-02: 38

## Common questions

### What is the io.github.cyberwareX/cyberwarex-council MCP server?

io.github.cyberwareX/cyberwarex-council is an MCP server listed in the public MCP registry as io.github.cyberwareX/cyberwarex-council. Second opinion for agents: 3-4 AI models answer, one verdict with confidence and dissent. This page covers its container image (ghcr.io/cyberwarex/cyberwarex-council).

### Is the io.github.cyberwareX/cyberwarex-council MCP server safe to use?

io.github.cyberwareX/cyberwarex-council scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.cyberwareX/cyberwarex-council MCP server expose?

io.github.cyberwareX/cyberwarex-council exposes 3 tools: council, council_deep, council_grounded. Their descriptions and schemas cost roughly 472 tokens of context every time the server is loaded.

### Is the io.github.cyberwareX/cyberwarex-council MCP server still maintained?

io.github.cyberwareX/cyberwarex-council is marked deprecated in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/cyberwarex/cyberwarex-council
- Repository: https://github.com/cyberwareX/cyberwarex-mcp
- Website: https://cyberwarex.com/assets/council-quickstart.html
- Changelog RSS feed: https://verifymcp.io/servers/cyberwarex-cyberwarex-council/ghcr-io-cyberwarex-cyberwarex-council.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyberwarex-cyberwarex-council/ghcr-io-cyberwarex-cyberwarex-council.json
- HTML version of this page: https://verifymcp.io/servers/cyberwarex-cyberwarex-council/ghcr-io-cyberwarex-cyberwarex-council