code-quorum (sdewell/code-quorum) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

C
Emerging
74/100
9 days ago

code-quorum

Enables multi-agent council workflows for coding assistants, providing parallel independent reviews, plans, brainstorms, validation, and research with strict read-only boundaries.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

sdewell

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 7 credentials: QUORUM_OPENALEX_API_KEY, CONTEXT7_API_KEY, GH_TOKEN, GITHUB_TOKEN, QUORUM_HF_TOKEN, HF_TOKEN, GEMINI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCODEX_HOME
configCODE_QUORUM_GEMINI_BACKENDcli (subscription) or sdk (metered GEMINI_API_KEY)
configCODE_QUORUM_GEMINI_MODELGemini seat model (an id from agy models)
configQUORUM_OPENALEX_EMAILOPENALEX_API_KEY or QUORUM_OPENALEX_API_KEY is required for normal OpenAlex use. QUORUM_OPENALEX_EMAIL identifies the client but does not replace the key.
🔐 secretQUORUM_OPENALEX_API_KEYOPENALEX_API_KEY or QUORUM_OPENALEX_API_KEY is required for normal OpenAlex use. QUORUM_OPENALEX_EMAIL identifies the client but does not replace the key.
🔐 secretCONTEXT7_API_KEYCONTEXT7_API_KEY is recommended because anonymous requests can be rate-limited.
🔐 secretGH_TOKENGH_TOKEN or GITHUB_TOKEN is recommended for higher limits. Private repositories are excluded.
🔐 secretGITHUB_TOKENGH_TOKEN or GITHUB_TOKEN is recommended for higher limits. Private repositories are excluded.
🔐 secretQUORUM_HF_TOKENHF_TOKEN or QUORUM_HF_TOKEN is recommended for account-level Hub limits. Private models are filtered out.
🔐 secretHF_TOKENHF_TOKEN or QUORUM_HF_TOKEN is recommended for account-level Hub limits. Private models are filtered out.
🔐 secretGEMINI_API_KEYGoogle AI subscription; metered GEMINI_API_KEY is an explicit SDK opt-in
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — q_plan_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); q_brainstorm_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); q_validate_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

6/12 tools referenced in tests (50%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/sdewell/code-quorum)](https://m8ven.ai/mcp/sdewell/code-quorum)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e6d874c9591c12ae4e1eba69207631ca43147cd8
code hash: 9236f259f46c88f464549dc6a21ff796290cc12ee8866ecd6424726889472ec2
verified: 9/1/2026, 5:16:10 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client