updated 2026-10-13 04:10 UTC

Claude Context

Repository by zilliztech

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

MCP Servers TypeScript Listed MIT

Is Claude Context safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.4 / 10
Provenance None
Signed commits 69%
Last push 91d ago
Compare Claude Context

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Claude Context scores 43.4/100 (Grade D), ranked #1142 of 1371 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; 69% of recent commits are signed; last pushed 2026-07-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Context could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Claude Context and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/zilliztech/claude-context, MIT, last pushed 2026-07-14. 69% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.4/10 (scanned Oct 12, 2026). The checks that decide who can get a change released:

    • Code Review7
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Claude Context is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Claude Context.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Claude Context’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Claude Context compares in MCP Servers

  1. #657 GitMCP 43.4 ±0
  2. #658 Himalayas Remote Jobs 43.4 ±0
  3. #659 Claude Context 43.4 this agent
  4. #660 Apple Docs MCP 43.3 −0.1
  5. #661 Deployhq MCP Server 43.0 −0.4

Bars show each HVTrust score; the tick marks Claude Context’s 43.4.

Where the 43.4 comes from

HVTrust dimensions vs the MCP Servers average

43.4 / 100 · 100.0% confidence

Claude Context MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.5 / 25
3.9 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
5.9 / 20
6.3 below avg 12.2
AdoptionLog-scaled stars · package downloads
9.8 / 20
2.4 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-13
Rank Moved
Rank dropped 10 spots (#1132 → #1142)
2026-10-12
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 12 spots (#1107 → #1119)
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.
Refresh maintenance signals The repo was last pushed 91 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Claude Context View MCP Servers Report missing data
50.9
Activity sub-score · out of 100
#659
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 →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed 91 days ago

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
12.6k
Forks
943
Last Push
2026-07-14
91 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
80
Rank Change
▼10
was #1132

Analysis

Activity Inputs

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

Common questions about Claude Context

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 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 Claude Context actively maintained?
Slowing down. Last push was 91 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
How this surface has changed

Detected changes to Claude 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-10-12
Activity Went Stale
No commits for 90 days

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 31Score 1Grade 1Stale 1
2026-10-13
Rank Moved
Rank dropped 10 spots (#1132 → #1142)
2026-10-12
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 12 spots (#1107 → #1119)
2026-09-27
Rank Moved
Rank dropped 15 spots (#1057 → #1072)
2026-09-23
Rank Moved
Rank dropped 618 spots (#426 → #1044)
2026-09-22
Rank Moved
Rank dropped 73 spots (#353 → #426)
2026-09-21
Rank Moved
Rank rose 687 spots (#1040 → #353)
2026-09-12
Rank Moved
Rank dropped 13 spots (#1009 → #1022)
2026-09-09
Rank Moved
Rank dropped 16 spots (#984 → #1000)
2026-09-08
Rank Moved
Rank dropped 20 spots (#964 → #984)
2026-09-07
Rank Moved
Rank dropped 36 spots (#928 → #964)
2026-09-06
Rank Moved
Rank dropped 14 spots (#914 → #928)
2026-09-05
Rank Moved
Rank dropped 52 spots (#862 → #914)
2026-09-04
Rank Moved
Rank dropped 33 spots (#829 → #862)
2026-09-03
Rank Moved
Rank dropped 52 spots (#777 → #829)
2026-09-02
Rank Moved
Rank dropped 39 spots (#738 → #777)
2026-09-01
Rank Moved
Rank dropped 32 spots (#706 → #738)
2026-08-31
Rank Moved
Rank dropped 37 spots (#669 → #706)
2026-08-30
Rank Moved
Rank dropped 19 spots (#650 → #669)
2026-08-29
Rank Moved
Rank dropped 43 spots (#607 → #650)
2026-08-28
Rank Moved
Rank dropped 20 spots (#587 → #607)
2026-08-27
Rank Moved
Rank dropped 12 spots (#575 → #587)
2026-08-26
Rank Moved
Rank dropped 86 spots (#489 → #575)
2026-08-24
Rank Moved
Rank dropped 12 spots (#475 → #487)
2026-08-22
Rank Moved
Rank rose 12 spots (#490 → #478)
2026-08-20
Rank Moved
Rank dropped 11 spots (#480 → #491)
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)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.4 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.4 · Raw JSON