Is MCP Local Rag safe to use?

MCP Local Rag has an HVTrust score of 24.2/100 (Grade D), ranked #859 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Local Rag?

MCP Local Rag scores 24.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 365 GitHub stars and is categorized under MCP Servers.

MCP Local Rag

shinpr/mcp-local-rag

Local-first RAG server for developers. Semantic + keyword search for code and technical docs. Works with MCP or CLI. Ful

MCP Servers TypeScript Grade D Listed MIT

24.2/100

Rank #859 of 1283

Compare MCP Local Rag

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 D · 1/5 signals

Last push

2026-08-12 · 0d ago

Recent change

Rank +2

Is MCP Local Rag safe? MCP Local Rag scores 24.2/100 (Grade D), ranked #859 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 22% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#418 MacOS MCP — 24.2 (D) → #419 Drawio MCP — 24.2 (D) → #421 Openwebninja MCP — 24.1 (D) → #422 MCP Codebase Index — 24.1 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-12

Rank Moved

Rank rose 18 spots (#877 → #859)

2026-08-10

Rank Moved

Rank dropped 58 spots (#819 → #877)

2026-08-08

Newly Listed

First tracked at rank #814

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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.

Compare with another agent Get email alerts for MCP Local Rag View MCP Servers Report missing data

70.2

Activity sub-score · out of 100

#420

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

365

Forks

Last Push

2026-08-12

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲18

was #877

Analysis

HVTrust Dimensions vs MCP Servers

24.2 / 100 · 40.0% confidence

MCP Local Rag MCP Servers average (761 agents)

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

1.1 / 25

3.9 below 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

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

18.8 / 20

6.4 above avg 12.4

AdoptionLog-scaled stars · package downloads

6.2 / 20

in line with avg 5.8

Activity Inputs

70.2 / 100

StarsRepository reach

15.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

21.3 / 25

CommunityFork signal

8.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

22%

of last 100 commits verified

Is MCP Local Rag safe?

Public trust evidence for MCP Local Rag 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 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?

No OpenSSF Scorecard data is currently published for MCP Local Rag. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

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?

22% 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-12

Rank Moved

Rank rose 18 spots (#877 → #859)

2026-08-10

Rank Moved

Rank dropped 58 spots (#819 → #877)

2026-08-08

Newly Listed

First tracked at rank #814

GitHub → npm: mcp-local-rag

Embed Badge Badge guide for maintainers →

For maintainers

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON