jcodemunch-mcp (jgravelle/jcodemunch-mcp) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 94 tools. No publisher has claimed this listing.

A
Trusted
98/100
8 days ago

jcodemunch-mcp

Cut AI token costs 95%+ on code exploration. The leading MCP server for precise, symbol-level GitHub code retrieval via tree-sitter AST. Works with Claude Code, Cursor & any MCP client. 313B+ tokens saved.

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

jgravelle

Source: Glama · also listed on github_topic

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 7 credentials: JCODEMUNCH_HTTP_TOKEN, ANTHROPIC_API_KEY, GOOGLE_API_KEY, JCODEMUNCH_LICENSE_KEY, OPENAI_API_KEY, GITHUB_TOKEN, GROQ_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.
configJCODEMUNCH_TOOL_SURFACE
configCODE_INDEX_PATH
configJCODEMUNCH_LIVE_JOURNAL
configJCODEMUNCH_HANDSHAKE_TIMEOUT
🔐 secretJCODEMUNCH_HTTP_TOKEN
configJCODEMUNCH_RATE_LIMIT
configJCODEMUNCH_MAX_SESSIONS
configJCODEMUNCH_SESSION_IDLE_TIMEOUT
configJCODEMUNCH_LOG_LEVEL
configJCODEMUNCH_LOG_FILE
configJCODEMUNCH_TRANSPORT
configJCODEMUNCH_HOST
configJCODEMUNCH_PORT
configJCODEMUNCH_EXTRA_EXTENSIONS
🔐 secretANTHROPIC_API_KEY
🔐 secretGOOGLE_API_KEY
configOPENAI_API_BASE
configPYTHONIOENCODING
configJCODEMUNCH_ORG_ID
🔐 secretJCODEMUNCH_LICENSE_KEY
configJCODEMUNCH_WATCH_DEBOUNCE_MS
configJCODEMUNCH_PARSE_BUDGET_SECONDS
configJCODEMUNCH_EMBED_MODEL
configGOOGLE_EMBED_MODEL
🔐 secretOPENAI_API_KEY
configOPENAI_EMBED_MODEL
configJCODEMUNCH_EAGER_EMBED_IMPORT
configGEMINI_EMBED_TASK_AWARE
configJCODEMUNCH_SCIP_MAX_ROWS
configREMOTE_CONTAINERS
configCODESPACES
configcontainer
🔐 secretGITHUB_TOKEN
🔐 secretGROQ_API_KEY
configSPEEDREVIEW_MODEL
configSPEEDREVIEW_SEVERITY
configSPEEDREVIEW_MAX_LENGTH
configSPEEDREVIEW_TOKEN_BUDGET
configSPEEDREVIEW_BASE_REF
configPR_NUMBER
configGITHUB_REPOSITORY
configGITHUB_WORKSPACE
configGITHUB_EVENT_PATH
// 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

94/94 tools missing one or more hints — order (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); menu (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); route (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +91 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.

Secrets never reach shell commands

3 secret values passed to a subprocess as an argument — no shell is invoked, so there is nothing to inject into

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

2 secret values sent to print

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 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/jgravelle/jcodemunch-mcp)](https://m8ven.ai/mcp/jgravelle/jcodemunch-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 63a621d639fe0a35100ba7335166dac584721e65
code hash: 48764e803f157544dba2b99e18cb522c0799655a9edc97ef9e47ce4405ffbfc7
verified: 9/3/2026, 11:02:29 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