code-context (nachogeinfor-ops/code-context) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

C
Emerging
74/100
10 days ago

code-context

An MCP server that provides dynamic codebase context to Claude Code through tools like hybrid search, recent changes, and symbol definitions, enhancing AI-assisted coding with local RAG.

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

⚡ 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

nachogeinfor-ops

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

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.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: POSTHOG_PROJECT_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: POSTHOG_PROJECT_API_KEY, OPENAI_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.
configCC_REPO_ROOT
configCC_CACHE_DIRor set explicitly to a path outside the sandbox:
🔐 secretPOSTHOG_PROJECT_API_KEY
configHF_HOME
configCC_NONINTERACTIVE
configCC_EMBEDDINGSlocal (or openai)
configCC_EMBEDDINGS_BACKEND
configCC_EMBEDDINGS_MODELall-MiniLM-L6-v2
configCC_INCLUDE_EXTENSIONS.py,.js,.ts,.jsx,.tsx,.go,.rs,.java,.c,.cpp,.h,.hpp,.md,.yaml,.yml,.json
configCC_RERANK_BATCH_SIZE
configCC_EMBED_BATCH_SIZE
configCC_TELEMETRYoff (opt-in; see below)
configCC_EMBED_CACHE_PERSISTENT
configCC_SEARCH_RANK
configCC_SYMBOL_RERANK
configCC_WATCH_GIT_OPS
configCC_INDEX_WORKERS
configCC_INDEXER_STRATEGY
🔐 secretOPENAI_API_KEY
configCC_MAX_FILE_BYTES
configCC_LOG_LEVEL
configCC_TOP_K_DEFAULT
configCC_CHUNK_LINES
configCC_CHUNK_OVERLAP
configCC_CHUNKERtreesitter (AST-aware for 9 languages: Python, JavaScript, TypeScript, Go, Rust, C#, Java, C++, Markdown — line fallback for the rest) — set line for v0.1.x behavior
configCC_KEYWORD_INDEX
configCC_RERANK
configCC_RERANK_MODEL
configCC_SYMBOL_INDEX
configCC_TRUST_REMOTE_CODE
configCC_BG_REINDEX
configCC_BG_IDLE_SECONDS
configCC_WATCH
configCC_WATCH_DEBOUNCE_MS) and then trigger a background reindex.
configCC_BM25_STOP_WORDS
configCC_SYMBOL_RANK
configCC_TELEMETRY_ENDPOINT
configCC_EMBED_CACHE_SIZE
configCC_LOG_FILE
configCC_HF_HUB_VERBOSE
configCC_EMBED_MAX_CHARS
configCC_HF_CACHE_DIR
// 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

8/8 tools missing one or more hints — search_repo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recent_changes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

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 2 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/nachogeinfor-ops/code-context)](https://m8ven.ai/mcp/nachogeinfor-ops/code-context)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 30ac9459a9a40bbff76a9bea3aedb445caeea95e
code hash: b53295f011bbb6d4d3177cd88efa5c755a898894747582fe0a62887d4d412a0a
verified: 9/2/2026, 9:11:14 PM
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