Is ChromaDB Remote MCP Server safe to use?

ChromaDB Remote MCP Server has an HVTrust score of 58.2/100 (Grade C), ranked #679 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ChromaDB Remote MCP Server?

ChromaDB Remote MCP Server scores 58.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

ChromaDB Remote MCP Server

meloncafe/chromadb-remote-mcp

Remote MCP server for ChromaDB

MCP Servers TypeScript Listed MIT

Is ChromaDB Remote MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.4 / 10

Provenance None

Signed commits 23%

Last push 7d ago

Compare ChromaDB Remote MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: ChromaDB Remote MCP Server scores 58.2/100 (Grade C), ranked #679 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.4/10; 23% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How ChromaDB Remote MCP Server compares in MCP Servers

#374 MCP Devkit Server 58.5 +0.3
#375 Joplin MCP Server 58.5 +0.3
#376 ChromaDB Remote MCP Server 58.2 this agent
#377 Blender MCP 58.2 ±0
#378 UniFi Gateway 58.1 −0.1

Bars show each HVTrust score; the tick marks ChromaDB Remote MCP Server’s 58.2.

Where the 58.2 comes from

HVTrust dimensions vs the MCP Servers average

58.2 / 100 · 100.0% confidence

ChromaDB Remote MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.9 / 25

2.4 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.1 / 17

0.9 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.6 / 20

5.5 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.8 / 20

0.6 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank rose 162 spots (#839 → #677)

2026-09-25

HVTrust Changed

HVTrust up 5.1pts (53.2 → 58.3)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for ChromaDB Remote MCP Server View MCP Servers Report missing data

53.2

Activity sub-score · out of 100

#376

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-19

7 days ago

Commits (4 wk)

Downloads (7d)

6,545

docker

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #677

Analysis

Activity Inputs

53.2 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

18.9 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.4 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

23%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about ChromaDB Remote MCP Server

ChromaDB Remote MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does ChromaDB Remote MCP Server publish package provenance?

No published build provenance is currently detected for ChromaDB Remote MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does ChromaDB Remote MCP Server have an OpenSSF Scorecard?

ChromaDB Remote MCP Server has an OpenSSF Scorecard score of 5.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is ChromaDB Remote MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does ChromaDB Remote MCP Server use?

ChromaDB Remote MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are ChromaDB Remote MCP Server's commits signed?

23% of the last 100 commits to ChromaDB Remote MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

ChromaDB Remote MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to ChromaDB Remote MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain ChromaDB Remote MCP Server?

For maintainers

HVTrust scores ChromaDB Remote MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank rose 162 spots (#839 → #677)

2026-09-25

HVTrust Changed

HVTrust up 5.1pts (53.2 → 58.3)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 25 spots (#805 → #830)

2026-09-23

HVTrust Changed

HVTrust up 24.8pts (28.7 → 53.5)

2026-09-22

Newly Listed

First tracked at rank #805

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade D → C

2026-09-19

Rank Moved

Rank rose 404 spots (#1220 → #816)

2026-09-19

HVTrust Changed

HVTrust up 17.5pts (36.3 → 53.8)

2026-09-18

Grade Changed

Trust grade C → D

2026-09-18

Rank Moved

Rank dropped 413 spots (#807 → #1220)

2026-09-18

HVTrust Changed

HVTrust down 17.7pts (54.0 → 36.3)

2026-09-17

Rank Moved

Rank rose 86 spots (#893 → #807)

2026-09-16

Grade Changed

Trust grade D → C

2026-09-16

Rank Moved

Rank rose 44 spots (#937 → #893)

2026-09-16

Activity Score Changed

Activity score up 11pts (43 → 54)

2026-09-14

Rank Moved

Rank rose 22 spots (#953 → #931)

2026-09-12

Rank Moved

Rank dropped 12 spots (#940 → #952)

2026-09-11

Rank Moved

Rank dropped 13 spots (#927 → #940)

2026-09-09

Rank Moved

Rank dropped 15 spots (#910 → #925)

2026-09-07

Rank Moved

Rank rose 321 spots (#1226 → #905)

2026-09-07

HVTrust Changed

HVTrust up 16.1pts (33.3 → 49.4)

2026-09-06

Rank Moved

Rank dropped 376 spots (#850 → #1226)

2026-09-06

HVTrust Changed

HVTrust down 16.2pts (49.5 → 33.3)

2026-09-05

Rank Moved

Rank dropped 56 spots (#794 → #850)

2026-09-04

Rank Moved

Rank dropped 30 spots (#764 → #794)

2026-09-03

Rank Moved

Rank dropped 47 spots (#717 → #764)

2026-09-02

Rank Moved

Rank dropped 38 spots (#679 → #717)

2026-09-01

Rank Moved

Rank dropped 24 spots (#655 → #679)

2026-08-31

Scorecard Added

OSSF Scorecard: 5.5/10

2026-08-31

Rank Moved

Rank rose 571 spots (#1226 → #655)

2026-08-31

HVTrust Changed

HVTrust up 30.2pts (19.6 → 49.8)

2026-08-30

Rank Moved

Rank dropped 23 spots (#1203 → #1226)

2026-08-29

Rank Moved

Rank dropped 21 spots (#1182 → #1203)

2026-08-28

Rank Moved

Rank dropped 17 spots (#1165 → #1182)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1152 → #1165)

2026-08-26

Rank Moved

Rank dropped 52 spots (#1100 → #1152)

2026-08-17

Rank Moved

Rank rose 10 spots (#1115 → #1105)

2026-08-16

Rank Moved

Rank dropped 24 spots (#1091 → #1115)

2026-08-10

Rank Moved

Rank dropped 62 spots (#1032 → #1094)

2026-08-08

Newly Listed

First tracked at rank #1027

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/chromadb-remote-mcp-server.svg)](https://hvtracker.net/agents/chromadb-remote-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/chromadb-remote-mcp-server"><img src="https://hvtracker.net/badge/chromadb-remote-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON