local-knowledge-suite (luutru433-coder/local-knowledge-suite) is an MCP server listed on the M8ven Trust Index. It scores 0 out of 100, grade F. It declares 4 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
0/100

local-knowledge-suite

Provides MCP tools for workspace initialization, health checks, context recall, and durable memory capture, enabling project-specific memory and shared company knowledge with citations.

→ luutru433-coder/local-knowledge-suite· 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

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

luutru433-coder

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// key findings
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 1 credential: MEMORIZER_EMBEDDING_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.
configCKB_ROOT
configCKB_CORS_ORIGINS
configCKB_CHAT_MODEL
configCKB_EMBEDDING_MODEL
configCKB_COVERAGE_THRESHOLD
configCKB_MIN_CLAIM_CONFIDENCE
configCKB_AVG_CLAIM_CONFIDENCE
configCKB_SESSION_HOURS
configCKB_CRAWLER_MAX_DEPTH
configCKB_CRAWLER_MAX_PAGES
configCKB_CRAWLER_DELAY
configCKB_CRAWLER_MAX_BYTES
configCKB_AUTO_PUBLISH
configCKB_SECURE_COOKIES
configCKB_CANONICAL_BRANCH
configCKB_LEASE_SECONDS
configCKB_HEARTBEAT_SECONDS
configCKB_CLAIM_BATCH_CHARS
configCKB_CLAIM_BATCH_SECTIONS
configMEMORIZER_EMBEDDING_URL
configMEMORIZER_EMBEDDING_MODEL
🔐 secretMEMORIZER_EMBEDDING_API_KEY
// 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

4/4 tools missing one or more hints — bootstrap_workspace (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); knowledge_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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 handlers catch errors

Only 0/4 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Readable source code

1 file appear obfuscated

Ship unminified, readable source.

Domain consistency

npm scope @local-knowledge-suite doesn't match GitHub owner luutru433-coder

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 6 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/luutru433-coder/local-knowledge-suite?variant=verified)](https://m8ven.ai/mcp/luutru433-coder/local-knowledge-suite)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: de7aa48f9fe6ca293ba2dbc076f41c03c49795be
code hash: 94ff44e7843b323218fe25ebaeb52dbac0c342a669fc2a95dc272a0c3d06f797
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