MCP Local Rag

Local-first RAG server for developers. Semantic + keyword search for code and technical docs. Works with MCP or CLI. Fully private, zero setup.

MCP Servers TypeScript Listed MIT

Is MCP Local Rag safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.4 / 10
Provenance None
Signed commits 30%
Last push yesterday
Advisories None known
Compare MCP Local Rag
Suggest a correction

In detail: MCP Local Rag scores 69.2/100 (Grade B), ranked #369 of 1378 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 5.4/10; 30% of recent commits are signed; no published advisory affects its latest release (mcp-local-rag); last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Local Rag 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.

Chain of custody

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

  1. Source Partly signed

    github.com/shinpr/mcp-local-rag, MIT, last pushed 2026-10-15. 30% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review1
    • Branch Protection4
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 8
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 6
  3. Published packages Linked, not attested

    • npm mcp-local-rag Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-local-rag 0.22.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-19 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues MCP Local Rag’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.

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 MCP Local Rag compares in MCP Servers

  1. #218 Search Console MCP 69.4 +0.2
  2. #219 Xcode: MCP Bridge Wrapper for Cursor 69.4 +0.2
  3. #220 MCP Local Rag 69.2 this agent
  4. #221 E18e MCP 69.2 ±0
  5. #222 1password MCP 69.2 ±0

Bars show each HVTrust score; the tick marks MCP Local Rag’s 69.2.

Where the 69.2 comes from

HVTrust dimensions vs the MCP Servers average

69.2 / 100 · 100.0% confidence

MCP Local Rag MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.2 / 25
2.3 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.6 above avg 12.3
AdoptionLog-scaled stars · package downloads
11.2 / 20
3.8 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-14
Rank Moved
Rank rose 10 spots (#382 → #372)
2026-10-10
Rank Moved
Rank rose 18 spots (#379 → #361)
2026-10-06
Rank Moved
Rank dropped 38 spots (#340 → #378)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.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.
74.5
Activity sub-score · out of 100
#220

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-10-16 16:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
415
Forks
80
Last Push
2026-10-15
yesterday
Commits (4 wk)
109
Downloads (7d)
4,508
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▼6
was #363

Analysis

Activity Inputs

74.5 / 100
StarsRepository reach
15.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
8.9 / 20

Common questions about MCP Local Rag

MCP Local Rag 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 MCP Local Rag publish package provenance?
No published build provenance is currently detected for MCP Local Rag. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Local Rag have an OpenSSF Scorecard?
MCP Local Rag has an OpenSSF Scorecard score of 5.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 MCP Local Rag actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Local Rag use?
MCP Local Rag ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Local Rag's commits signed?
30% of the last 100 commits to MCP Local Rag 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
MCP Local Rag appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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 MCP Local Rag'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-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Local Rag?

For maintainers

HVTrust scores MCP Local Rag 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 27HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-14
Rank Moved
Rank rose 10 spots (#382 → #372)
2026-10-10
Rank Moved
Rank rose 18 spots (#379 → #361)
2026-10-06
Rank Moved
Rank dropped 38 spots (#340 → #378)
2026-10-02
Rank Moved
Rank rose 13 spots (#353 → #340)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 310 spots (#653 → #343)
2026-09-23
HVTrust Changed
HVTrust up 36.9pts (32.2 → 69.1)
2026-09-22
Newly Listed
First tracked at rank #653
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Scorecard Added
OSSF Scorecard: 5.7/10
2026-09-19
Grade Changed
Trust grade D → B
2026-09-19
Rank Moved
Rank rose 816 spots (#1167 → #351)
2026-09-19
HVTrust Changed
HVTrust up 29.0pts (39.9 → 68.9)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1145 → #1161)
2026-09-08
Rank Moved
Rank dropped 12 spots (#1133 → #1145)
2026-09-06
Rank Moved
Rank dropped 11 spots (#1113 → #1124)
2026-09-05
Rank Moved
Rank rose 158 spots (#1271 → #1113)
2026-09-05
HVTrust Changed
HVTrust up 15.3pts (23.8 → 39.1)
2026-09-04
Rank Moved
Rank dropped 10 spots (#1261 → #1271)
2026-09-03
Rank Moved
Rank dropped 32 spots (#1229 → #1261)
2026-09-02
Rank Moved
Rank dropped 38 spots (#1191 → #1229)
2026-09-01
Rank Moved
Rank dropped 38 spots (#1153 → #1191)
2026-08-31
Rank Moved
Rank dropped 29 spots (#1124 → #1153)
2026-08-30
Rank Moved
Rank dropped 43 spots (#1081 → #1124)
2026-08-29
Rank Moved
Rank dropped 43 spots (#1038 → #1081)
2026-08-28
Rank Moved
Rank dropped 31 spots (#1007 → #1038)
2026-08-27
Rank Moved
Rank dropped 29 spots (#978 → #1007)
2026-08-26
Rank Moved
Rank dropped 114 spots (#864 → #978)
2026-08-24
Rank Moved
Rank dropped 10 spots (#848 → #858)
2026-08-23
Rank Moved
Rank rose 16 spots (#864 → #848)
2026-08-17
Rank Moved
Rank rose 12 spots (#885 → #873)
2026-08-16
Rank Moved
Rank dropped 25 spots (#860 → #885)
2026-08-13
Rank Moved
Rank dropped 17 spots (#850 → #867)
2026-08-12
Rank Moved
Rank rose 27 spots (#877 → #850)
2026-08-10
Rank Moved
Rank dropped 58 spots (#819 → #877)
2026-08-08
Newly Listed
First tracked at rank #814

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 69.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-local-rag.svg)](https://hvtracker.net/agents/mcp-local-rag)
HTML:
<a href="https://hvtracker.net/agents/mcp-local-rag"><img src="https://hvtracker.net/badge/mcp-local-rag.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.4 · Raw JSON