Claude Context

Code search MCP for Claude Code. Make entire codebase the context for any coding agent.

MCP Servers TypeScript Grade D Listed MIT
48.7/100
Rank #480 of 1308
Compare Claude Context

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-14 · 36d ago
Recent change
Rank +5

Is Claude Context safe? Claude Context scores 48.7/100 (Grade D), ranked #480 of 1308 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 3.2/10; 69% of recent commits are signed; last pushed 2026-07-14. 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
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-19
Rank Moved
Rank dropped 12 spots (#468 → #480)
2026-08-17
Rank Moved
Rank rose 12 spots (#479 → #467)
2026-08-13
Grade Changed
Trust grade C → D
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.2/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.
Refresh maintenance signals The repo was last pushed 36 days ago. Fresh activity helps separate stable projects from stale ones.
58.5
Activity sub-score · out of 100
#168

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 →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed 36 days ago

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
12.4k
Forks
914
Last Push
2026-07-14
36 days ago
Commits (4 wk)
0?
Downloads (7d)
HN mentions (30d)
Open Issues
78
Rank Change
▼12
was #468

Analysis

HVTrust Dimensions vs MCP Servers

48.7 / 100 · 100.0% confidence

Claude Context MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.4 / 25
2.4 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
11.2 / 17
2.4 above avg 8.8
Maintenance60% last-push freshness · 40% commit activity
9.6 / 20
2.8 below avg 12.4
AdoptionLog-scaled stars · package downloads
9.8 / 20
4.0 above avg 5.8

Activity Inputs

58.5 / 100
StarsRepository reach
24.6 / 30
FreshnessLast push recency
20.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.8 / 20

Supply Chain Trust

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

Is Claude Context safe?

Public trust evidence for Claude 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 Claude Context publish package provenance?
No published build provenance is currently detected for Claude 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 Claude Context have an OpenSSF Scorecard?
Claude Context has an OpenSSF Scorecard score of 3.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 Claude Context actively maintained?
Slowing down. Last push was 36 days ago — keep an eye on whether activity resumes.
What license does Claude Context use?
Claude Context ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Context's commits signed?
69% of the last 100 commits to Claude 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
Claude 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
2 tags
Broad capability areas detected.
  • code
  • filesystem
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

Maintain Claude Context?

For maintainers

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

Reputation Timeline

Signal history
Rank 7Grade 2Listed 1HVTrust 1Scorecard 1Score 1
2026-08-19
Rank Moved
Rank dropped 12 spots (#468 → #480)
2026-08-17
Rank Moved
Rank rose 12 spots (#479 → #467)
2026-08-13
Grade Changed
Trust grade C → D
2026-08-13
Rank Moved
Rank dropped 28 spots (#439 → #467)
2026-08-13
Activity Score Changed
Activity score down 8pts (67 → 59)
2026-08-12
Rank Moved
Rank rose 14 spots (#453 → #439)
2026-08-10
Rank Moved
Rank dropped 18 spots (#435 → #453)
2026-08-08
Rank Moved
Rank dropped 109 spots (#325 → #434)
2026-07-15
Scorecard Added
OSSF Scorecard: 3.2/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 114 spots (#401 → #287)
2026-07-15
HVTrust Changed
HVTrust up 29.5pts (22.4 → 51.9)
2026-07-14
Newly Listed
First tracked at rank #401

Embed Badge Badge guide for maintainers →

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