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

Limited view

75/100

1 month ago

jdocmunch-mcp

Item: jdocmunch-mcp
Rating: 75
Author: M8ven

The leading, most token-efficient MCP server for documentation exploration and retrieval via structured section indexing

→ jgravelle/jdocmunch-mcp · listed on github_topic

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 push why connect →

Who stands behind it

jgravelle

Source: github_topic · also listed on Glama, github_code

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

GitHub Glama GitHub

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 5 credentials: GITHUB_TOKEN, JDOCMUNCH_OPENAI_COMPAT_API_KEY, GOOGLE_API_KEY, OPENAI_API_KEY, ANTHROPIC_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.

configJDOCMUNCH_TOOL_PROFILE

configJDOCMUNCH_DISABLED_TOOLS

configDOC_INDEX_PATH

configJDOCMUNCH_GIT_TIMEOUT

🔐 secretGITHUB_TOKEN

configGITHUB_EVENT_NAME

configGITHUB_SHA

configGITHUB_REF_NAME

configGITHUB_RUN_ID

configPR_HEAD_SHA

configJDOCMUNCH_META_FIELDS

configJDOCMUNCH_HOOK_MIN_SIZE

configJDOCMUNCH_HOOK_DEBOUNCE_SECONDS

configJDOCMUNCH_HOOK_MAX_REINDEX

configJDOCMUNCH_HOOK_LOG

configJDOCMUNCH_HOOK_INCLUDE_SOURCE_ROOTS

configJDOCMUNCH_OPENAI_COMPAT_URL

configJDOCMUNCH_OPENAI_COMPAT_MODEL

🔐 secretJDOCMUNCH_OPENAI_COMPAT_API_KEY

configJDOCMUNCH_OPENAI_COMPAT_BATCH_SIZE

configJDOCMUNCH_ALLOW_PAID_EMBEDDINGS

configJDOCMUNCH_EMBEDDING_PROVIDER

🔐 secretGOOGLE_API_KEY

🔐 secretOPENAI_API_KEY

configJDOCMUNCH_ST_MODEL

configJDOCMUNCH_BM25_K1

configJDOCMUNCH_BM25_B

configJDOCMUNCH_REPLAY_LOG

configJDOCMUNCH_SHARE_SAVINGS

configJDOCMUNCH_SESSION_TOKEN_BUDGET

configJDOCMUNCH_PERF_TELEMETRY

configJDOCMUNCH_PERF_TELEMETRY_MAX_ROWS

🔐 secretANTHROPIC_API_KEY

configJDOCMUNCH_ALLOW_PAID_SUMMARIES

configJDOCMUNCH_SUMMARIZER_PROVIDER

// 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

65/65 tools missing one or more hints — call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); index_local (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); doc_index_repo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +62 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.

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 3 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/jdocmunch-mcp)](https://m8ven.ai/mcp/jgravelle/jdocmunch-mcp)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: a6a3e6839f422cf2ebfdfb99402612564bc20bd7

code hash: e10ac8404ccb57126fbf77755f3dffedd84b857e5530be8026b1ef21b8823ca3

verified: 8/7/2026, 2:14:31 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