Codex–Claude Council
NPM · CODEX-CLAUDE-COUNCIL
ChatGPT (Codex CLI) and Claude (Claude Code) discuss until they agree, on your own subscriptions.
Available components
Last scanned (20 hours ago)
Scores higher than 93% of npm servers
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 3 of 9 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hamza-aziz-ai/codex-claude-council). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
- 27 Oct 26 −8
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: pass → unverified ▼ functional
- Schema quality: 638 → 514 ▲ functional
- 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 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.13.5 → 0.15.1 functional
- Package version: 0.13.5 → 0.15.0 functional
- 25 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.13.4 → 0.13.5 functional
- 24 Oct 26 +1
- Security disclosure: fail → pass ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/codex-claude-council@0.21.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | hamza-aziz-ai/codex-claude-council |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hamza-aziz-ai/codex-claude-council/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3516007942 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b4bb4155fdbde0aae18195d461e99176a507a31ca3488e80b2b118b89e28146faa7e7d741111c7cfa4ff88e605e168d1198744546b58fce1e947c61c8 |
Background: How many MCP packages publish verified provenance →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
council_ask Ask the Codex–Claude council ~1,079
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_ask_claude Ask Claude only ~617
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_ask_codex Ask Codex (ChatGPT) only ~669
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_cancel Stop a running council ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | The job_id a council tool returned while still working. Omit to use the most recent job. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_debate Codex–Claude debate transcript ~1,025
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_join Discuss with the other model yourself ~974
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_result Get a running council's answer ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | The job_id a council tool returned while still working. Omit to use the most recent job. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
council_turn Send your turn to the council ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| council_id | string | yes | The council_id from the message you are replying to. |
| text | string | yes | Your complete reply to that message, written by you. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The answer (council_debate: its JSON), or the message to act on; the same as the text content. |
No examples provided.
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.
npm · codex-claude-council
claude mcp add hamza-aziz-ai-codex-claude-council -- npx -y codex-claude-council
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 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.