ContextStream

Intelligence without context is unreliable. Autonomy without context is chaos. And context without trust becomes surveil

MCP Servers Rust Grade B Listed MIT
79.9/100
Rank #98 of 1320
Compare ContextStream

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Provenance +11

Is ContextStream safe? ContextStream scores 79.9/100 (Grade B), ranked #98 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.3/10; 17% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
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)
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
54.8
Activity sub-score · out of 100
#39

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-04 13:33 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
41
Forks
10
Last Push
2026-09-04
today
Commits (4 wk)
16
Downloads (7d)
852
npm
HN mentions (30d)
Open Issues
0
Rank Change
▼1
was #97

Analysis

HVTrust Dimensions vs MCP Servers

79.9 / 100 · 100.0% confidence

ContextStream MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.5 / 25
8.0 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.7 / 17
2.9 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
16.9 / 20
4.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.8 / 20
1.6 above avg 6.2

Activity Inputs

54.8 / 100
StarsRepository reach
9.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
15.3 / 25
CommunityFork signal
4.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
7.3 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
17%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 4
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 10
Security-Policy 10
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 9

Is ContextStream safe?

Public supply-chain signals for ContextStream are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but ContextStream carries less obvious unverified-evidence risk than projects with thin signals.
Does ContextStream publish package provenance?
Yes. ContextStream's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does ContextStream have an OpenSSF Scorecard?
ContextStream has an OpenSSF Scorecard score of 7.3/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?
17% 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-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 12HVTrust 2Listed 1Scorecard 1Score 1Grade 1Provenance 1
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 79.9 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