Cognitive Core (mocartlex-wq/cognitive-core) is an MCP server listed on the M8ven Trust Index. It scores 39 out of 100, grade F. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
39/100

Cognitive Core

Enables AI agents with persistent, multi-layer memory, multi-agent collaboration rooms, and video generation, all accessible via MCP tools.

→ mocartlex-wq/cognitive-core· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

mocartlex-wq

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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
🚨
Secret credentials may flow to a network call
13 flows detected: COGCORE_DEPLOY_GITHUB_TOKEN, COGCORE_ROOM_KEY, DEEPSEEK_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: /opt/cognitive-core/.env
🔐
You'll be asked for 16 credentials: COGCORE_API_KEY, COGCORE_DEPLOY_GITHUB_TOKEN, COGCORE_ROOM_KEY, ORCHESTRATOR_API_KEY, DEEPSEEK_API_KEY, POSTGRES_PASSWORD, ORCH_KEY, ROOMS_ADMIN_KEY, COGCORE_CONFIG_KEY, COGCORE_SECRETS_MASTER_KEY, GITEA_ADMIN_TOKEN, COGNITIVE_API_KEY, MAILAPI_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, YOOKASSA_SECRET_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.
configCORS_ORIGINS_CSV
configCOGCORE_SERVER_URL
🔐 secretCOGCORE_API_KEY
configWHISPER_MODEL_SIZE
configROOMS_BASE_URL
configAGENT_API_KEYSАутентификация: X-API-Key per-agent через в .env
configCOGCORE_DEPLOY_ADMIN_OWNER_IDS
🔐 secretCOGCORE_DEPLOY_GITHUB_TOKEN
configCOGCORE_DEPLOY_REPO
configCOGCORE_DEPLOY_BASE_BRANCH
configCOGCORE_URL
configCOGCORE_AGENT_ID
🔐 secretCOGCORE_ROOM_KEY
configCOGCORE_TIMEOUT
configCOGCORE_LOG
configCOGCORE_DATABASE_URL
configORCH_LOG_LEVEL
🔐 secretORCHESTRATOR_API_KEY
🔐 secretDEEPSEEK_API_KEY
configCOGCORE_API_BASE
configORCHESTRATOR_AGENT_ID
configOWNER_AGENT_ID
configOWNER_EMAIL
configDEEPSEEK_BASE_URL
configDEEPSEEK_MODEL
configORCH_POLL_INTERVAL_S
configORCH_APPROVAL_TIMEOUT_S
configORCH_LOG_TO_L1
configORCH_DRY_RUN
configORCH_STATE_DIR
🔐 secretPOSTGRES_PASSWORD
configCOGCORE_RUNTIME_LOG
configCOGCORE_RUNTIME_HISTORY
configCOGCORE_MAX_INBOUND_CHARS
configCOGCORE_LIVE_AGENT_WINDOW_SEC
configORCH_PORT
configCOGCORE_BASE
configCOGCORE_INTERNAL
configORCH_EXEC_TIMEOUT_S
configORCH_WAKE_WAIT_S
🔐 secretORCH_KEY
configAGENT_KEY_LAPTOP
configORCH_OWNER_CODE
configROOMS_PORT
configPROXY_FALLBACK_AFTER
configROOMS_MAX_MESSAGE_CHARS
configCOGCORE_ENV_FILE
🔐 secretROOMS_ADMIN_KEY
configPUBLIC_BASE_URL
🔐 secretCOGCORE_CONFIG_KEY
configNATS_URL
configREPLICATION_STREAM
🔐 secretCOGCORE_SECRETS_MASTER_KEY
configEMBEDDING_USE_GPU
configGITEA_URL
🔐 secretGITEA_ADMIN_TOKEN
configWHISPER_CACHE_DIR
configFRAMES_PER_VIDEO
configFRAME_MAX_WIDTH
configMAX_VIDEO_DURATION_SEC
configWHISPER_DEVICE
configCOGNITIVE_URL
🔐 secretCOGNITIVE_API_KEY
🔐 secretMAILAPI_KEY
configMAILAPI_FROM
configMAILAPI_FROM_NAME
configMAILAPI_RATE_LIMIT_PER_HOUR
configHEALTH_PORT
configROOMS_CORS_ORIGINS
configROOMS_CORS_MAX_AGE
configROOMS_CORS_CREDS
configROOMS_RL_PER_MINUTE
configROOMS_RL_BURST
configROOMS_RL_KEY_HEADER
configROOMS_RL_BYPASS_PATHS
🔐 secretSTRIPE_SECRET_KEY
🔐 secretSTRIPE_WEBHOOK_SECRET
configSTRIPE_PRICE_PRO
configSTRIPE_PRICE_ENTERPRISE
configYOOKASSA_SHOP_ID
🔐 secretYOOKASSA_SECRET_KEY
configYANDEX_CLOUD_FOLDER_ID
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPG_DSN
// 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

10/10 tools missing one or more hints — cognitive_room_create (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cognitive_room_join (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cognitive_room_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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

Only 0/10 tools referenced in tests (0%)

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

No access to sensitive paths

Reads sensitive paths: /opt/cognitive-core/.env

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Secrets not logged

3 secret values sent to logger.warning

Redact or omit secret values from log output.

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 5 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/mocartlex-wq/cognitive-core?variant=verified)](https://m8ven.ai/mcp/mocartlex-wq/cognitive-core)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0a0b4c6ec8f55f7b90a6914394ebc7ea32b38acf
code hash: d102317b008d55fcdf5ac69149bc202b9a2a092da395f516c189279b37d9f70e
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