ChromaDB Remote MCP Server (meloncafe/chromadb-remote-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 19 tools. No publisher has claimed this listing.

C
Emerging
74/100

ChromaDB Remote MCP Server

A Streamable HTTP MCP server that provides remote access to ChromaDB for AI assistants like Claude. Enables semantic search and vector database operations from mobile devices and remote locations.

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

meloncafe

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
2 flows detected: GOOGLE_OAUTH_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: CHROMA_AUTH_TOKEN, EMBEDDING_API_KEY, GEMINI_API_KEY, GOOGLE_OAUTH_CLIENT_SECRET, MCP_AUTH_TOKEN, RERANKER_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.
configALLOWED_ORIGINSComma-separated list of allowed origins (DNS rebinding protection) - No
configALLOW_INSECURE_NO_AUTHtrue is explicitly set.
configCHROMA_ADMIN_TOOLS_ENABLED## Admin — opt-in (=true)
configCHROMA_ALLOW_DESTRUCTIVE_OPS## Destructive — opt-in (=true)
🔐 secretCHROMA_AUTH_TOKENChromaDB auth token (if ChromaDB requires auth) - No
configCHROMA_DATABASEChromaDB database default_database No
configCHROMA_DISTRIBUTED_TOOLS_ENABLED## Distributed/Cloud-only — opt-in (=true)
configCHROMA_HOSTChromaDB host (internal) chromadb No
configCHROMA_PORTChromaDB port (internal) 8000 No
configCHROMA_REST_PROXY_ENABLEDtrue is set. When disabled, all /api/ requests return 404.
configCHROMA_TENANTChromaDB tenant default_tenant No
configCONFIDENCE_THRESHOLDDefault min_score (0-1). Tool argument has priority.
configEMBEDDING_API_BASEOpenAI-compatible endpoint base URL (Ollama / TEI / Voyage / Together / vLLM).
🔐 secretEMBEDDING_API_KEYBearer key for openai_compatible or voyage providers.
configEMBEDDING_DIMENSIONSVector dimensions. Required for external mode; Gemini accepts 768/1536/3072.
configEMBEDDING_MODELProvider-specific model id. Stored in collection metadata.
configEMBEDDING_PROVIDERchromadb-default (English-only, default) / external / openai_compatible / gemini / voyage
🔐 secretGEMINI_API_KEYGoogle AI Studio API key for the gemini provider.
configGOOGLE_OAUTH_CLIENT_ID
🔐 secretGOOGLE_OAUTH_CLIENT_SECRET
configLEGACY_COLLECTION_COMPATtrue to allow read-only access to legacy v1 collections. Writes are still rejected.
configLOG_LEVEL
🔐 secretMCP_AUTH_TOKENFor production use, generate a secure token for in .env:
configOAUTH_PROXY_ALLOW_PRESHARED_CLIENT
configOAUTH_PROXY_BASE_URL
configOAUTH_PROXY_ENABLED
configOAUTH_PROXY_GOOGLE_SCOPES
configOAUTH_PROXY_REDIRECT_URI_ALLOWLIST
configOAUTH_PROXY_STORE_MAX
configOIDC_AUDIENCESet to the resource identifier (typically your MCP server's public URL).
configOIDC_ISSUERSSet (comma-separated issuer URLs) or OIDC_PRESET=google,github,microsoft.
configOIDC_PRESETSet OIDC_ISSUERS (comma-separated issuer URLs) or =google,github,microsoft.
configOIDC_SCOPESComma-separated scopes for the Protected Resource Metadata.
configPING_TIMEOUT
configRATE_LIMIT_MAXMax requests per IP per 15 minutes 100 No
configREQUEST_TIMEOUT
configRERANKER_API_BASEOpenAI-compatible /rerank endpoint. Reranker is fail-soft.
🔐 secretRERANKER_API_KEYOptional bearer key for the reranker.
configRERANKER_MODELReranker model id (default bge-reranker-v2-m3).
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

19/19 tools missing one or more hints — chroma_list_collections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); chroma_create_collection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); chroma_peek_collection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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/meloncafe/chromadb-remote-mcp)](https://m8ven.ai/mcp/meloncafe/chromadb-remote-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f6f9ce4f4fab1c170676acf2ff1cb35e0f2aa08f
code hash: 6eb426e16d86a798fcda6d72c121dd0c68cbf1101590b19611f89a7a2fb7cbe7
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