cognitive-lead-hq (mokhtarabadi/cognitive-lead-hq) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 28 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
74/100

cognitive-lead-hq

The centralized Headquarters for the Cognitive Lead AI multi-agent system. Features hallucination-resistant system prompts, MCP servers, and strict Agent Skills.

→ mokhtarabadi/cognitive-lead-hq· listed on github_repo_search

Caution. Specific findings reduced this grade. They are listed on the page. 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

mokhtarabadi

Source: github_repo_search · also listed on github_code

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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 1 credential: BRAIN_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.
configBRAIN_WORKSPACE_ROOT
configBRAIN_SYSTEM_PROMPT
configBRAIN_MODEL
configBRAIN_MAX_TOKENS
🔐 secretBRAIN_API_KEY
configBRAIN_SESSIONS_ROOT
configBRAIN_TEMPERATURE
configBRAIN_API_BASE
configBRAIN_REASONING_EFFORT
configDECISION_REPO_PATH
configDECISION_NO_PULL
configDECISION_TEMPERATURE
configDECISION_MODEL
// 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

28/28 tools missing one or more hints — get_context_bundle (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); grep_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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.

Destructive tools are labelled

3 tools perform destructive updates without destructiveHint — bundle_tasks deletes at line 1387 (output_path.unlink(missing_ok=True)); store_memory deletes at line 221 (os.unlink(temp_path)); delete_memory deletes at line 258 (file_path.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

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 Verified](https://m8ven.ai/badge/mcp/mokhtarabadi/cognitive-lead-hq?variant=verified)](https://m8ven.ai/mcp/mokhtarabadi/cognitive-lead-hq)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 69f38a056b28f00ed8d9a7a5f460ba7cfd15b167
code hash: 7cd9d8c9aaeea7af6e6e591cd54fb90ba5b7ac017664e8f8a8bc5e332e043854
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