Claude Context (zilliztech/claude-context) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
2 months ago

Claude Context

Claude Context is an MCP plugin that adds semantic code search to Claude Code and other AI coding agents, giving them deep context from your entire codebase.

→ zilliztech/claude-context· listed on mcp_so

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

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

zilliztech

Source: mcp.so

Maintenance & responsiveness
as of 2026-08-19
Issue response: no maintainer replies in sample
Issues closed (90d): 2 · 141 open
Releases (90d): none
Contributor retention: 1/3 stayed · 19 active
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

mcp.so

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 4 credentials: OPENAI_API_KEY, GITHUB_TOKEN, MOONSHOT_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.
configE2E_CODEBASE_PATH
configE2E_LOG_FILE
configEMBEDDING_BATCH_SIZE
configHYBRID_MODE
configMILVUS_COLLECTION_LIMIT_CHECK_TIMEOUT_MS
configWORKER_ID
🔐 secretOPENAI_API_KEYe =sk-your-openai-api-key \
configMILVUS_ADDRESSe =your-zilliz-cloud-public-endpoint \
🔐 secretGITHUB_TOKEN
🔐 secretMOONSHOT_API_KEY
🔐 secretANTHROPIC_API_KEY
// 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

9/9 tools missing one or more hints — index_codebase (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); clear_index (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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 handlers catch errors

4/5 tool handlers wrap calls in try/catch (80%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 1/9 tools referenced in tests (11%)

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

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/zilliztech/claude-context)](https://m8ven.ai/mcp/zilliztech/claude-context)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 627eb2be339723926d5b468698a8f5cc0da21167
code hash: b7a4c5ce4deb5beb16c2811b00fda85261f691813bf4de15f29e41d08e8b539d
verified: 6/30/2026, 9:56:39 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