ContextStream

Persistent memory, semantic search, and shared project context for AI agents with traceable sources and scoped access. Carry decisions, lessons, and intent across sessions and tools.

MCP Servers Rust Listed MIT

Is ContextStream safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.2 / 10
Provenance None
Signed commits 36%
Last push yesterday
Compare ContextStream
Suggest a correction

In detail: ContextStream scores 67.4/100 (Grade B), ranked #388 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 7.2/10; 36% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How ContextStream compares in MCP Servers

  1. #229 MCP Server Couchbase 67.5 +0.1
  2. #230 Sfcc Dev MCP 67.5 +0.1
  3. #231 ContextStream 67.4 this agent
  4. #232 Laravel Boost 67.4 ±0
  5. #233 Better Telegram MCP 67.3 −0.1

Bars show each HVTrust score; the tick marks ContextStream’s 67.4.

Where the 67.4 comes from

HVTrust dimensions vs the MCP Servers average

67.4 / 100 · 100.0% confidence

ContextStream MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
0.5 above 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
14.6 / 17
2.4 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
18.5 / 20
6.4 above avg 12.1
AdoptionLog-scaled stars · package downloads
7.7 / 20
in line with 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-26
Provenance Removed
Package provenance attestation no longer detected
2026-09-26
Grade Changed
Trust grade A → B
2026-09-26
Rank Moved
Rank dropped 271 spots (#117 → #388)
Maintainer Checklist
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.
60.2
Activity sub-score · out of 100
#231

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
43
Forks
11
Last Push
2026-09-25
yesterday
Commits (4 wk)
42
Downloads (7d)
694
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
▼271
was #117

Analysis

Activity Inputs

60.2 / 100
StarsRepository reach
9.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.4 / 25
CommunityFork signal
5.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
7.2 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
36%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 6
CII-Best-Practices 0
Code-Review 5
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 9
Security-Policy 10
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 9

Common questions about ContextStream

ContextStream 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 ContextStream publish package provenance?
No published build provenance is currently detected for ContextStream. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ContextStream have an OpenSSF Scorecard?
ContextStream has an OpenSSF Scorecard score of 7.2/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 ContextStream actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does ContextStream use?
ContextStream ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ContextStream's commits signed?
36% of the last 100 commits to ContextStream 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
ContextStream appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
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
high confidence
Match
Published package metadata matches the tracked repo
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 ContextStream'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-26
Provenance Removed
Package provenance attestation no longer detected
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-02
Provenance Added
Package provenance attestation detected

Maintain ContextStream?

For maintainers

HVTrust scores ContextStream 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.

Reputation Timeline

Signal history
Rank 16HVTrust 4Grade 4Listed 2Provenance 2Scorecard 1Score 1Delisted 1MCP 1Provenance 1
2026-09-26
Provenance Removed
Package provenance attestation no longer detected
2026-09-26
Grade Changed
Trust grade A → B
2026-09-26
Rank Moved
Rank dropped 271 spots (#117 → #388)
2026-09-26
HVTrust Changed
HVTrust down 15.2pts (82.6 → 67.4)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 533 spots (#646 → #113)
2026-09-23
HVTrust Changed
HVTrust up 50.3pts (32.3 → 82.6)
2026-09-22
Newly Listed
First tracked at rank #646
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank rose 10 spots (#108 → #98)
2026-09-05
Grade Changed
Trust grade B → A
2026-09-05
Rank Moved
Rank dropped 21 spots (#97 → #118)
2026-09-02
Provenance Added
Package provenance attestation detected
2026-09-02
Grade Changed
Trust grade D → B
2026-09-02
Rank Moved
Rank rose 866 spots (#962 → #96)
2026-09-02
HVTrust Changed
HVTrust up 40.6pts (38.5 → 79.1)
2026-09-01
Rank Moved
Rank dropped 12 spots (#950 → #962)
2026-09-01
Activity Score Changed
Activity score up 5pts (48 → 53)
2026-08-31
Rank Moved
Rank dropped 31 spots (#919 → #950)
2026-08-30
Rank Moved
Rank dropped 43 spots (#876 → #919)
2026-08-29
Rank Moved
Rank dropped 47 spots (#829 → #876)
2026-08-28
Scorecard Added
OSSF Scorecard: 4.7/10
2026-08-28
Rank Moved
Rank rose 302 spots (#1131 → #829)
2026-08-28
HVTrust Changed
HVTrust up 16.8pts (20.5 → 37.3)
2026-08-27
Rank Moved
Rank dropped 17 spots (#1114 → #1131)
2026-08-26
Rank Moved
Rank dropped 68 spots (#1046 → #1114)
2026-08-16
Rank Moved
Rank dropped 14 spots (#1038 → #1052)
2026-08-13
Rank Moved
Rank dropped 10 spots (#1027 → #1037)
2026-08-12
Rank Moved
Rank dropped 10 spots (#1017 → #1027)
2026-08-10
Rank Moved
Rank dropped 56 spots (#956 → #1012)
2026-08-08
Newly Listed
First tracked at rank #946

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.4 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/contextstream.svg)](https://hvtracker.net/agents/contextstream)
HTML:
<a href="https://hvtracker.net/agents/contextstream"><img src="https://hvtracker.net/badge/contextstream.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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