jambavan (beingmartinbmc/jambavan) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

jambavan

An MCP server that provides coding models with a live code index, inferred code graph, durable memory, and surgical tools to help them leverage their existing reasoning and coding abilities effectively.

→ beingmartinbmc/jambavan· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

beingmartinbmc

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

Glama

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.
// 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.
configJAMBAVAN_ALLOW_BASHoff Registers bash
configJAMBAVAN_ALLOW_OUTSIDE_ROOToff Disables direct-path project-root containment
configJAMBAVAN_ALLOW_SECRETSoff Allows direct paths matching the secret-file guard
configJAMBAVAN_ALLOW_WRITEwrite_file, patch_file, jambavan_compress_prompt =1
configJAMBAVAN_BASH_INHERIT_ENVoff Passes full host env to bash
configJAMBAVAN_DEV_MODEfull Default dev_rules level (lite, full, ultra)
configJAMBAVAN_MAX_OUTPUT_CHARS100000 Global cap on tool output
configJAMBAVAN_MAX_READ_BYTES5242880 Max file size read_file loads
configJAMBAVAN_MEMORY_HOME~/.jambavan/memory Override for the root-independent OKF archive
configJAMBAVAN_MEMPALACE_COMMANDmempalace-mcp Executable for explicit read-only MemPalace calls
configJAMBAVAN_ROOT/tmp/react node dist/benchmark.js
configJAMBAVAN_SCOPEGit-derived Validated clone-independent scope override
configJAMBAVAN_TOKEN_BUDGET8000 Max approximate cl100k_base tokens in jambavan_context
configMEMPALACE_FAKE_MODE
configMEMPALACE_FAKE_STATE_FILE
configSECRET_THING
// 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

18/18 tools missing one or more hints — jambavan_awaken (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jambavan_index (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jambavan_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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

10/18 tools referenced in tests (56%)

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

Shell command execution

8 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 4 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/beingmartinbmc/jambavan)](https://m8ven.ai/mcp/beingmartinbmc/jambavan)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8b507598a750bedd19f9e92a39ceef7f2b8efb48
code hash: 1290cfc622e7c060846ed258181bb55ee90df24d1450a9602e8b898d51a07a27
verified: 8/7/2026, 4:43: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