mcp-brain-tools (j3k0/mcp-elastic-memory) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Caution
74/100
14 days ago

mcp-brain-tools

Provides a scalable knowledge graph implementation for Model Context Protocol using Elasticsearch, enabling AI models to store and query information with advanced search capabilities, memory-like behavior, and multi-zone architecture.

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

j3k0

Source: modelscope

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
🚨
Secret credentials may flow to a network call
3 flows detected: GROQ_API_KEY, AI_API_BASE. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: AI_API_KEY, ES_PASSWORD, GROQ_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@1.1.3GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@1.1.3GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

high@modelcontextprotocol/sdk@0.6.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configAI_API_BASEThe hook uses the same ES_NODE, AI_API_KEY/GROQ_API_KEY, , and AI_MODEL env vars (set them in the env block of your settings, or export them in your shell profile).
🔐 secretAI_API_KEYThe hook uses the same ES_NODE, /GROQ_API_KEY, AI_API_BASE, and AI_MODEL env vars (set them in the env block of your settings, or export them in your shell profile).
configAI_MODELThe hook uses the same ES_NODE, AI_API_KEY/GROQ_API_KEY, AI_API_BASE, and env vars (set them in the env block of your settings, or export them in your shell profile).
configES_NODEOr point to your own instance via environment variable.
🔐 secretES_PASSWORDElasticsearch password
configES_USERNAMEElasticsearch username
🔐 secretGROQ_API_KEY"": "your-key-here"
configGROQ_MODELSopenai/gpt-oss-120b,llama-3.3-70b-versatile Comma-separated model list
configKG_DEFAULT_ZONEdefault Default memory zone
configKG_INDEX_PREFIXknowledge-graph Elasticsearch index prefix
configMEMORY_FILE_PATH
configMEMORY_HOOK_AI_TIMEOUT
configMEMORY_HOOK_CONTEXT_LINES
configMEMORY_HOOK_ES_TIMEOUT
configMEMORY_HOOK_MAX_RESULTS
configMEMORY_HOOK_MIN_SCORE
configMEMORY_HOOK_MIN_WORDS
configMEMORY_HOOK_ZONES
configMEMORY_SAVE_AI_TIMEOUT
configMEMORY_SAVE_MIN_ASSISTANT_WORDS
configMEMORY_SAVE_TRANSCRIPT_LINES
// 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

29/29 tools missing one or more hints — create_entities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_relations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_observations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 1/29 tools referenced in tests (3%)

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

Secrets stay with their owner

2 secret/sensitive values flow into network calls (AI_API_BASE → dynamic, AI_API_BASE → dynamic) (1 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@0.6.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 7 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/j3k0-mcp-elastic-memory-fxsrsd?variant=verified)](https://m8ven.ai/mcp/j3k0-mcp-elastic-memory-fxsrsd)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 708d00f3a8c0a8887f58466d25f6676820ae641c
code hash: a79899276b9b7a89a7f6521a5715b40e1b8eaf61e5707ded497bdaff3d410436
verified: 8/13/2026, 9:04:41 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