Is Context+ safe to use?

Context+ has an HVTrust score of 41.9/100 (Grade D), ranked #1105 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Context+?

Context+ scores 41.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.0k GitHub stars and is categorized under MCP Servers.

Context+

forloopcodes/contextplus

Semantic Intelligence for Large-Scale Engineering. Context+ is an MCP server designed for developers who demand 99% accu

MCP Servers TypeScript Grade D Listed MIT

41.9/100

Rank #1105 of 1328

Compare Context+

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-07-13 · 57d ago

Recent change

Rank +8

Is Context+ safe? Context+ scores 41.9/100 (Grade D), ranked #1105 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.4/10; 26% of recent commits are signed; last pushed 2026-07-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#648 MCP Power Automate — 42.0 (D) → #649 Gopls MCP — 41.9 (D) → #651 Tijori Finance MCP — 41.9 (D) → #652 Glean Remote MCP Server — 41.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-08

Rank Moved

Rank dropped 15 spots (#1090 → #1105)

2026-09-07

Rank Moved

Rank dropped 28 spots (#1062 → #1090)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1046 → #1062)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.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.

Refresh maintenance signals The repo was last pushed 57 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Context+ View MCP Servers Report missing data

47.2

Activity sub-score · out of 100

#650

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

2.0k

Forks

167

Last Push

2026-07-13

57 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼15

was #1090

Analysis

HVTrust Dimensions vs MCP Servers

41.9 / 100 · 100.0% confidence

Context+ MCP Servers average (778 agents)

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

4.3 / 25

5.6 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.5 / 17

1.5 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

8.2 / 20

4.0 below avg 12.2

AdoptionLog-scaled stars · package downloads

7.9 / 20

1.0 above avg 6.9

Activity Inputs

47.2 / 100

StarsRepository reach

19.8 / 30

FreshnessLast push recency

17.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.4 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

26%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 4

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 5

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is Context+ safe?

Public trust evidence for Context+ is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Context+ publish package provenance?

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

Does Context+ have an OpenSSF Scorecard?

Context+ has an OpenSSF Scorecard score of 2.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 Context+ actively maintained?

Slowing down. Last push was 57 days ago — keep an eye on whether activity resumes.

What license does Context+ use?

Context+ ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Context+'s commits signed?

26% of the last 100 commits to Context+ 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

Context+ appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

1 tags

Broad capability areas detected.

code

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 Context+'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

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain Context+?

For maintainers

HVTrust scores Context+ 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-08

Rank Moved

Rank dropped 15 spots (#1090 → #1105)

2026-09-07

Rank Moved

Rank dropped 28 spots (#1062 → #1090)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1046 → #1062)

2026-09-05

Rank Moved

Rank dropped 39 spots (#1007 → #1046)

2026-09-04

Rank Moved

Rank dropped 24 spots (#983 → #1007)

2026-09-03

Rank Moved

Rank dropped 61 spots (#922 → #983)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Rank Moved

Rank dropped 41 spots (#881 → #922)

2026-09-01

Rank Moved

Rank dropped 30 spots (#851 → #881)

2026-08-31

Rank Moved

Rank dropped 30 spots (#821 → #851)

2026-08-30

Rank Moved

Rank dropped 33 spots (#788 → #821)

2026-08-29

Rank Moved

Rank dropped 47 spots (#741 → #788)

2026-08-28

Rank Moved

Rank dropped 28 spots (#713 → #741)

2026-08-27

Rank Moved

Rank dropped 22 spots (#691 → #713)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.4/10

2026-08-26

Rank Moved

Rank rose 469 spots (#1160 → #691)

2026-08-26

HVTrust Changed

HVTrust up 23.8pts (18.4 → 42.2)

2026-08-16

Rank Moved

Rank dropped 28 spots (#1121 → #1149)

2026-08-12

Rank Moved

Rank dropped 37 spots (#1085 → #1122)

2026-08-12

Activity Score Changed

Activity score down 6pts (57 → 51)

2026-08-10

Newly Listed

First tracked at rank #1080

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/context.svg)](https://hvtracker.net/agents/context)
            
HTML:
            <a href="https://hvtracker.net/agents/context"><img src="https://hvtracker.net/badge/context.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