# Codex–Claude Council (npm · codex-claude-council)

ChatGPT (Codex CLI) and Claude (Claude Code) discuss until they agree, on your own subscriptions.

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `codex-claude-council`: 91/100 (this document), [markdown](https://verifymcp.io/servers/hamza-aziz-ai-codex-claude-council/codex-claude-council.md), [page](https://verifymcp.io/servers/hamza-aziz-ai-codex-claude-council/codex-claude-council)

## Channel facts

- Registry: `npm`
- Package: `codex-claude-council`
- Version: `0.21.1`
- 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**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 9 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to hamza-aziz-ai/codex-claude-council).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5148 tokens (~514/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Codex–Claude Council MCP server?

Codex–Claude Council runs locally as an npm package, launched with npx -y codex-claude-council. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add hamza-aziz-ai-codex-claude-council -- npx -y codex-claude-council
```

### Cursor

```json
{
  "mcpServers": {
    "hamza-aziz-ai-codex-claude-council": {
      "command": "npx",
      "args": [
        "-y",
        "codex-claude-council"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hamza-aziz-ai-codex-claude-council": {
      "command": "npx",
      "args": [
        "-y",
        "codex-claude-council"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hamza-aziz-ai-codex-claude-council -- npx -y codex-claude-council
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hamza-aziz-ai-codex-claude-council": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "codex-claude-council"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hamza-aziz-ai-codex-claude-council --command npx --arg -y --arg codex-claude-council
```

### Hermes

```yaml
mcp_servers:
  hamza-aziz-ai-codex-claude-council:
    command: "npx"
    args: ["-y", "codex-claude-council"]
```

### Netclaw

```json
{
  "McpServers": {
    "hamza-aziz-ai-codex-claude-council": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "codex-claude-council"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hamza-aziz-ai-codex-claude-council -t stdio -c npx -a -y codex-claude-council
```

### Other

```json
{
  "mcpServers": {
    "hamza-aziz-ai-codex-claude-council": {
      "command": "npx",
      "args": [
        "-y",
        "codex-claude-council"
      ]
    }
  }
}
```

## 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-05 (score 91, +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-11-03 (score 90, +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-31 (score 89, +1)

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

### 2026-10-29 (score 88, +1)

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

### 2026-10-28 (score 87, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.88

### 2026-10-27 (score 61, −8)

- [security regression] Known CVEs: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Schema quality: 638 → 514
- [functional improvement] Schema quality: unverified → 100
- [functional] Package version: 0.15.1 → 0.21.1
- [functional] Package version: 0.15.1 → 0.21.0
- [functional] Package version: 0.15.1 → 0.20.0
- [functional] Package version: 0.15.1 → 0.19.0
- [functional] Package version: 0.15.1 → 0.17.0
- [functional] Package version: 0.13.4 → 0.15.1

### 2026-10-26 (score 69, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.13.5 → 0.15.1
- [functional] Package version: 0.13.5 → 0.15.0

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

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.33 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 0.13.4 → 0.13.5

## MCP tools (8)

### `council_ask` (~1079 tokens)

Ask the Codex–Claude council

Get one cross-checked answer from Codex (ChatGPT) and Claude: each answers on its own, then they reply to each other until both agree, and one writes the final answer that the other checks. Use it for decisions, reviews and questions where a second model's check is worth minutes of waiting; for a quick single opinion use council_ask_codex or council_ask_claude, and for the whole discussion use council_debate. It runs the user's local Codex and Claude Code CLIs on their own subscriptions, so it uses both plans' quota, and takes minutes; a call still running after about 50 s returns a job_id for council_result. With workspace, both models read the project but never change it. Each model keeps its session between calls, so it remembers earlier questions.

Input parameters:

- `claude_effort` (string): Optional Claude effort level override. Omit to use the configured default; set only when the user asks for a specific one.
- `claude_model` (string): Optional Claude model override: an alias such as opus, sonnet or fable, or a full model name. Omit to use the configured default; set only when the user asks for a specific one.
- `claude_session_id` (string): Optional: a Claude Code session the user already has: its UUID (as shown by `/status`) or the name they gave it with `/rename`; on another machine, user@host:<id or name> (runs there through ssh), to…
- `codex_effort` (string): Optional Codex reasoning effort override. Omit to use the configured default; set only when the user asks for a specific one.
- `codex_model` (string): Optional Codex (ChatGPT) model override, e.g. gpt-5.6-sol. Omit to use the configured default; set only when the user asks for a specific one.
- `codex_session_id` (string): Optional: a Codex session the user already has: its id (as shown by `/status`) or the name they gave it with `/rename`; on another machine, user@host:<id or name> (runs there through ssh), to continu…
- `max_rounds` (integer): Optional limit on the exchange. After the two independent answers, each model replies to the other's latest message, round after round, until both agree; then the synthesizer writes the final answer…
- `network` (boolean): Optional: whether Codex's shell commands may reach the network (for example to call an API or fetch live data), still read-only on disk. Omit to use the configured default (off unless the user change…
- `question` (string, required): The question, with any context the models need.
- `skill` (string): Optional: the name of an installed skill both models may use for this question, at the steps where they judge it is needed, including any sub-agents it calls for; for several skills, their names sepa…
- `synthesizer` (string): Optional: which model writes the final answer ("codex" is ChatGPT); the other checks it. Omit to use the configured default (Claude unless the user changed it).
- `web_search` (boolean): Optional: whether the models may search the web and read web pages. Omit to use the configured default (on unless the user changed it). Pass false only when the user asks for no internet access.
- `workspace` (string): Absolute path of the project folder you are working in. Both models then work in it in plan mode: they read it (files, search, read-only commands such as git log and diff) but never change it. Pass i…

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_debate` (~1025 tokens)

Codex–Claude debate transcript

Run the same council as council_ask but return the whole discussion as JSON: both opening answers, every exchange with each model's reply and verdict, the check of the final answer, and the settings used. Use it when the user wants to see where the models disagreed or how they converged; use council_ask when only the answer matters, since the transcript is long. Same cost and timing as council_ask: both plans' quota, minutes, and a job_id for council_result if it is still running after about 50 s.

Input parameters:

- `claude_effort` (string): Optional Claude effort level override. Omit to use the configured default; set only when the user asks for a specific one.
- `claude_model` (string): Optional Claude model override: an alias such as opus, sonnet or fable, or a full model name. Omit to use the configured default; set only when the user asks for a specific one.
- `claude_session_id` (string): Optional: a Claude Code session the user already has: its UUID (as shown by `/status`) or the name they gave it with `/rename`; on another machine, user@host:<id or name> (runs there through ssh), to…
- `codex_effort` (string): Optional Codex reasoning effort override. Omit to use the configured default; set only when the user asks for a specific one.
- `codex_model` (string): Optional Codex (ChatGPT) model override, e.g. gpt-5.6-sol. Omit to use the configured default; set only when the user asks for a specific one.
- `codex_session_id` (string): Optional: a Codex session the user already has: its id (as shown by `/status`) or the name they gave it with `/rename`; on another machine, user@host:<id or name> (runs there through ssh), to continu…
- `max_rounds` (integer): Optional limit on the exchange. After the two independent answers, each model replies to the other's latest message, round after round, until both agree; then the synthesizer writes the final answer…
- `network` (boolean): Optional: whether Codex's shell commands may reach the network (for example to call an API or fetch live data), still read-only on disk. Omit to use the configured default (off unless the user change…
- `question` (string, required): The question, with any context the models need.
- `skill` (string): Optional: the name of an installed skill both models may use for this question, at the steps where they judge it is needed, including any sub-agents it calls for; for several skills, their names sepa…
- `synthesizer` (string): Optional: which model writes the final answer ("codex" is ChatGPT); the other checks it. Omit to use the configured default (Claude unless the user changed it).
- `web_search` (boolean): Optional: whether the models may search the web and read web pages. Omit to use the configured default (on unless the user changed it). Pass false only when the user asks for no internet access.
- `workspace` (string): Absolute path of the project folder you are working in. Both models then work in it in plan mode: they read it (files, search, read-only commands such as git log and diff) but never change it. Pass i…

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_ask_codex` (~669 tokens)

Ask Codex (ChatGPT) only

Ask Codex (ChatGPT) alone, through the user's Codex CLI signed in with ChatGPT, and return its answer. Use it for a quick second opinion from ChatGPT; use council_ask when the answer should also be cross-checked by Claude, or council_ask_claude for Claude alone. It uses the user's ChatGPT plan and usually answers within a minute (longer at high effort, when it returns a job_id for council_result). With workspace it reads the project but never changes it; its session carries over between calls.

Input parameters:

- `effort` (string): Optional Codex reasoning effort override. Omit to use the configured default; set only when the user asks for a specific one.
- `model` (string): Optional Codex (ChatGPT) model override, e.g. gpt-5.6-sol. Omit to use the configured default; set only when the user asks for a specific one.
- `network` (boolean): Optional: whether Codex's shell commands may reach the network (for example to call an API or fetch live data), still read-only on disk. Omit to use the configured default (off unless the user change…
- `question` (string, required): The question, with any context the models need.
- `session_id` (string): Optional: a Codex session the user already has: its id (as shown by `/status`) or the name they gave it with `/rename`; on another machine, user@host:<id or name> (runs there through ssh), to continu…
- `skill` (string): Optional: the name of an installed skill both models may use for this question, at the steps where they judge it is needed, including any sub-agents it calls for; for several skills, their names sepa…
- `web_search` (boolean): Optional: whether the models may search the web and read web pages. Omit to use the configured default (on unless the user changed it). Pass false only when the user asks for no internet access.
- `workspace` (string): Absolute path of the project folder you are working in. Both models then work in it in plan mode: they read it (files, search, read-only commands such as git log and diff) but never change it. Pass i…

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_ask_claude` (~617 tokens)

Ask Claude only

Ask Claude alone, through the user's Claude Code CLI signed in with a Claude subscription, and return its answer. Use it for a quick second opinion from Claude, for example from Codex or ChatGPT; use council_ask when the answer should also be cross-checked by Codex, or council_ask_codex for Codex alone. It uses the user's Claude plan and usually answers within a minute (longer at high effort, when it returns a job_id for council_result). With workspace it reads the project in plan mode and never changes it; its session carries over between calls.

Input parameters:

- `effort` (string): Optional Claude effort level override. Omit to use the configured default; set only when the user asks for a specific one.
- `model` (string): Optional Claude model override: an alias such as opus, sonnet or fable, or a full model name. Omit to use the configured default; set only when the user asks for a specific one.
- `question` (string, required): The question, with any context the models need.
- `session_id` (string): Optional: a Claude Code session the user already has: its UUID (as shown by `/status`) or the name they gave it with `/rename`; on another machine, user@host:<id or name> (runs there through ssh), to…
- `skill` (string): Optional: the name of an installed skill both models may use for this question, at the steps where they judge it is needed, including any sub-agents it calls for; for several skills, their names sepa…
- `web_search` (boolean): Optional: whether the models may search the web and read web pages. Omit to use the configured default (on unless the user changed it). Pass false only when the user asks for no internet access.
- `workspace` (string): Absolute path of the project folder you are working in. Both models then work in it in plan mode: they read it (files, search, read-only commands such as git log and diff) but never change it. Pass i…

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_join` (~974 tokens)

Discuss with the other model yourself

Take part in the council yourself, in this conversation, with everything you already know, instead of a separate session of your model: you are one member and the plugin runs the other model (Codex if you are Claude, Claude if you are Codex), optionally continuing the user's own session of it. The steps are the same as council_ask (answer independently, then reply to each other's latest message until both agree, then write and check the final answer). Whenever it is your turn, this tool (or council_turn / council_result) returns the council's message to you: write your reply yourself and send it with council_turn. Use this when the user wants you to discuss with the other model, or gives the id of their session of the other model; use council_ask instead when the user wants a council of two separate sessions. Only the other model runs a CLI session; your turns are written here, in this conversation.

Input parameters:

- `max_rounds` (integer): Optional limit on the exchange. After the two independent answers, each model replies to the other's latest message, round after round, until both agree; then the synthesizer writes the final answer…
- `me` (string): Which model you are: "claude" if you are Claude (Claude Code, Claude Desktop), "codex" if you are Codex or ChatGPT. The other model is the one the plugin runs.
- `network` (boolean): Optional: whether Codex's shell commands may reach the network (for example to call an API or fetch live data), still read-only on disk. Omit to use the configured default (off unless the user change…
- `other_effort` (string): Optional effort override for the other model (Codex: none, minimal, low, medium, high, xhigh; Claude: low, medium, high, xhigh, max). Omit to use the configured default; set only when the user asks f…
- `other_model` (string): Optional model override for the other model. Omit to use the configured default; set only when the user asks for a specific one.
- `other_session_id` (string): Optional: the id or /rename name of the user's own session of the other model (a Codex session if you are Claude, a Claude Code session if you are Codex), or user@host:<id or name> for one on another…
- `question` (string, required): The question, with any context the models need.
- `skill` (string): Optional: the name of an installed skill both models may use for this question, at the steps where they judge it is needed, including any sub-agents it calls for; for several skills, their names sepa…
- `synthesizer` (string): Optional: which model writes the final answer, "claude" or "codex" (you or the other model); the other checks it. Omit to write it yourself (the host); pass it only when the user names who should wri…
- `web_search` (boolean): Optional: whether the models may search the web and read web pages. Omit to use the configured default (on unless the user changed it). Pass false only when the user asks for no internet access.
- `workspace` (string): Absolute path of the project folder you are working in. Both models then work in it in plan mode: they read it (files, search, read-only commands such as git log and diff) but never change it. Pass i…

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_turn` (~138 tokens)

Send your turn to the council

Send your reply to the council's latest message, after council_join, council_turn or council_result returned your turn, and wait for the next step. Only for councils started with council_join; the text is passed to the other model as written, so write the complete reply yourself. If the council is not waiting for you, it says so and you call council_result instead; if the next step takes longer than about 50 s, call council_result with the council_id.

Input parameters:

- `council_id` (string, required): The council_id from the message you are replying to.
- `text` (string, required): Your complete reply to that message, written by you.

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_result` (~142 tokens)

Get a running council's answer

Wait for a job that returned status working with a job_id (from council_ask, council_debate, council_ask_codex, council_ask_claude or council_join), and return its answer, or with council_join your next turn. Waits up to about 50 s and returns as soon as something is ready; if the job is still working, call it again. Use it instead of asking the same question again, which would start a second job and use the plans twice. Waiting uses no model quota.

Input parameters:

- `job_id` (string): The job_id a council tool returned while still working. Omit to use the most recent job.

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

### `council_cancel` (~117 tokens)

Stop a running council

Stop a running job (a council_ask, council_debate, council_ask_codex, council_ask_claude or council_join): its Codex and Claude CLI processes are ended and its progress is discarded, so its answer can no longer be retrieved. Use it when the user asks to stop, or a council is no longer needed; to check on a job instead, use council_result.

Input parameters:

- `job_id` (string): The job_id a council tool returned while still working. Omit to use the most recent job.

Output parameters:

- `council_id` (string): With your_turn: the council to reply to with council_turn.
- `job_id` (string): With working or stopped: the job to wait for, or the one stopped.
- `status` (string): done: text is the answer. working: still running; call council_result with job_id. your_turn (council_join): text is the council's message; reply with council_turn and council_id. stopped: council_ca…
- `text` (string): The answer (council_debate: its JSON), or the message to act on; the same as the text content.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/hamza-aziz-ai-codex-claude-council/codex-claude-council#diagnostics

## Score history

- 2026-11-05: 91
- 2026-11-04: 90
- 2026-11-03: 90
- 2026-11-02: 89
- 2026-11-01: 89
- 2026-10-31: 89
- 2026-10-30: 88
- 2026-10-29: 88
- 2026-10-28: 87
- 2026-10-27: 61
- 2026-10-26: 69
- 2026-10-25: 84
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 38
- 2026-10-12: 39

## Common questions

### What is the Codex–Claude Council MCP server?

Codex–Claude Council is an MCP server listed in the public MCP registry as io.github.hamza-aziz-ai/codex-claude-council. ChatGPT (Codex CLI) and Claude (Claude Code) discuss until they agree, on your own subscriptions. This page covers its npm package (codex-claude-council).

### Is the Codex–Claude Council MCP server safe to use?

Codex–Claude Council scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Codex–Claude Council MCP server expose?

Codex–Claude Council exposes 8 tools: council_ask, council_debate, council_ask_codex, council_ask_claude, council_join, and 3 more. Their descriptions and schemas cost roughly 4,761 tokens of context every time the server is loaded.

### Is the Codex–Claude Council MCP server still maintained?

Codex–Claude Council is still listed as active 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.

### What licence is the Codex–Claude Council MCP server under?

Codex–Claude Council declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/codex-claude-council
- Socket report: https://socket.dev/npm/package/codex-claude-council
- Repository: https://github.com/hamza-aziz-ai/codex-claude-council
- Changelog RSS feed: https://verifymcp.io/servers/hamza-aziz-ai-codex-claude-council/codex-claude-council.xml
- Changelog JSON feed: https://verifymcp.io/servers/hamza-aziz-ai-codex-claude-council/codex-claude-council.json
- HTML version of this page: https://verifymcp.io/servers/hamza-aziz-ai-codex-claude-council/codex-claude-council