io.github.TheStevenJohnstone/ai-consensus
NPM · AI-CONSENSUS-CONNECTOR
Standing review layer for coding agents: Claude, GPT and Gemini debate, return consensus + dissent.
Available components
Last scanned (7 hours ago)
Scores higher than 55% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 106 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 288 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 −2
- Stability: pass → 0.83 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/ai-consensus-connector@0.12.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
cancel_ai_consensus_run ~29
Cancel an in-progress AI Consensus run by id.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
check_ai_consensus_connection ~62
Zero-cost setup check: verifies the API is reachable, your AI Consensus key is accepted, and (on bring-your-own-keys plans) which provider keys are present. Does NOT start a deliberation and costs nothing. Use right after installing the connector.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
consult_ai_consensus ~133
Route a decision, question, or task through three frontier AIs (Claude, GPT, Gemini) that answer independently, then cross-examine each other — returning one recommendation plus the strongest dissent. Intended as a STANDING part of the development loop: consult it as a matter of course for any decision of consequence (architecture, design, approach, tricky bugs, anything whose cost of being wrong is real) — not just rare emergencies. Purely mechanical edits do not need a run. A run takes a few minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | The decision, question, or task to run through AI Consensus. |
No output schema declared.
No examples provided.
get_ai_consensus_result ~31
Fetch the status/result of an AI Consensus run by id.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
start_ai_consensus ~33
Start an AI Consensus run without waiting; returns a run id to collect later.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.TheStevenJohnstone/ai-consensus MCP server?
io.github.TheStevenJohnstone/ai-consensus runs locally as an npm package, launched with npx -y ai-consensus-connector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ai-consensus-connector
claude mcp add thestevenjohnstone-ai-consensus -- npx -y ai-consensus-connector
What is the io.github.TheStevenJohnstone/ai-consensus MCP server?
io.github.TheStevenJohnstone/ai-consensus is an MCP server listed in the public MCP registry as io.github.TheStevenJohnstone/ai-consensus. Standing review layer for coding agents: Claude, GPT and Gemini debate, return consensus + dissent. This page covers its npm package (ai-consensus-connector).
Is the io.github.TheStevenJohnstone/ai-consensus MCP server safe to use?
io.github.TheStevenJohnstone/ai-consensus scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.TheStevenJohnstone/ai-consensus MCP server expose?
io.github.TheStevenJohnstone/ai-consensus exposes 5 tools: consult_ai_consensus, start_ai_consensus, get_ai_consensus_result, cancel_ai_consensus_run, check_ai_consensus_connection. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Is the io.github.TheStevenJohnstone/ai-consensus MCP server still maintained?
io.github.TheStevenJohnstone/ai-consensus 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 io.github.TheStevenJohnstone/ai-consensus MCP server under?
io.github.TheStevenJohnstone/ai-consensus declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.