Marrow (desikai-lab/Marrow) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Limited view
69/100
2 months ago

Marrow

Marrow is a persistent multi-project memory backend that provides AI agents with MCP tools for semantic code navigation, task backlog management, and versioned artifact storage. It enables seamless, token-optimized context sharing and asynchronous handoffs between different AI models working on the same codebase.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

desikai-lab

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 3 credentials: GITHUB_TOKEN, SECRET_TOKEN, MCP_SECRET_TOKEN
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.
🔐 secretGITHUB_TOKEN
🔐 secretSECRET_TOKENyour-strong-random-secret
configEMBEDDING_MODEL_CODESentence-transformer model for code skeleton embeddings BAAI/bge-small-en-v1.5
configEMBEDDING_MODEL_NAME
configEMBEDDING_DIMENSIONSEmbedding vector dimensions — must match the chosen model 384
configMAX_EMBED_CHARSMaximum characters to embed per chunk 2000
configAGENT_PROFILE_ENGINE_ENABLED
configVECT_DEBOUNCE_SECONDSDebounce delay before vectorizing a changed file 0.5
configTASKS_DIR/data # leave as-is for Docker; data persists in a named volume
configLOG_LEVEL
configHOST
configMAINTENANCE_INTERVAL_SECONDS
configMCP_DEBUG_TRANSPORT
configBASE_URL
configWORKER_OUTBOX_PATH
configWORKER_FLUSH_INTERVAL_SECONDS
configWORKER_FLUSH_CONCURRENCY
🔐 secretMCP_SECRET_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

24/24 tools missing one or more hints — add_tasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_tasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_task_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +21 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 inputs are validated

22/24 tool handlers declare input schemas (92%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/24 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.

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 Score](https://m8ven.ai/badge/mcp/desikai-lab-marrow-6yv107)](https://m8ven.ai/mcp/desikai-lab-marrow-6yv107)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e0610a8671f09c54574f6b8e6db9e1e5a72d192c
code hash: 302c1c6b0f7d1465f435c9236c0c1e13b7a0a8aa9bfcea918dd5df7d2bfd0e7a
verified: 6/25/2026, 9:48:56 AM
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