Is Local FAISS MCP Server safe to use?

Local FAISS MCP Server has an HVTrust score of 54.6/100 (Grade C), ranked #799 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Local FAISS MCP Server?

Local FAISS MCP Server scores 54.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 34 GitHub stars and is categorized under MCP Servers.

Local FAISS MCP Server

nonatofabio/local_faiss_mcp

Local FAISS vector store as an MCP server – Agent Memory, drop-in local semantic search for Claude / Copilot / Agents.

MCP Servers Python Listed MIT

Is Local FAISS MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10

Provenance Attested

Signed commits 19%

Last push 155d ago

Compare Local FAISS MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Local FAISS MCP Server scores 54.6/100 (Grade C), ranked #799 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 2.9/10; 19% of recent commits are signed; last pushed 2026-04-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Local FAISS MCP Server compares in MCP Servers

#442 Ris MCP Ts 54.6 ±0
#443 Vaaya 54.6 ±0
#444 Local FAISS MCP Server 54.6 this agent
#445 Reddit Research MCP 54.5 −0.1
#446 Tradingview MCP 54.5 −0.1

Bars show each HVTrust score; the tick marks Local FAISS MCP Server’s 54.6.

Where the 54.6 comes from

HVTrust dimensions vs the MCP Servers average

54.6 / 100 · 100.0% confidence

Local FAISS MCP Server MCP Servers average (775 agents)

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

12.1 / 25

1.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.0 / 17

1.2 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

1.7 / 20

10.4 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.8 / 20

1.4 below avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 11 spots (#791 → #802)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.9/10. Tighten the weakest checks to improve public safety evidence.

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 155 days ago. Fresh activity helps separate stable projects from stale ones.

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

18.2

Activity sub-score · out of 100

#444

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 C 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-04-24

155 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #802

Analysis

Activity Inputs

18.2 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

3.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

19%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Local FAISS MCP Server

Public trust evidence for Local FAISS MCP Server 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 Local FAISS MCP Server publish package provenance?

Yes. Local FAISS MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Local FAISS MCP Server have an OpenSSF Scorecard?

Local FAISS MCP Server has an OpenSSF Scorecard score of 2.9/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 Local FAISS MCP Server actively maintained?

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

What license does Local FAISS MCP Server use?

Local FAISS MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Local FAISS MCP Server's commits signed?

18% of the last 100 commits to Local FAISS MCP Server 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

medium confidence

Implemented

Local FAISS MCP Server 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 Local FAISS MCP Server'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

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Local FAISS MCP Server?

For maintainers

HVTrust scores Local FAISS MCP Server 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-25

Rank Moved

Rank dropped 11 spots (#791 → #802)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 474 spots (#1260 → #786)

2026-09-23

HVTrust Changed

HVTrust up 39.9pts (15.0 → 54.9)

2026-09-22

Newly Listed

First tracked at rank #1260

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank rose 16 spots (#802 → #786)

2026-09-13

Rank Moved

Rank dropped 19 spots (#789 → #808)

2026-09-11

Rank Moved

Rank dropped 10 spots (#772 → #782)

2026-09-09

Rank Moved

Rank dropped 21 spots (#746 → #767)

2026-09-07

Rank Moved

Rank dropped 46 spots (#695 → #741)

2026-09-06

Rank Moved

Rank dropped 12 spots (#683 → #695)

2026-09-05

Rank Moved

Rank dropped 75 spots (#608 → #683)

2026-09-04

Rank Moved

Rank dropped 35 spots (#573 → #608)

2026-09-03

Rank Moved

Rank dropped 33 spots (#540 → #573)

2026-09-02

Rank Moved

Rank dropped 17 spots (#523 → #540)

2026-09-01

Rank Moved

Rank dropped 13 spots (#510 → #523)

2026-08-31

Rank Moved

Rank dropped 35 spots (#475 → #510)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.9/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 132 spots (#607 → #475)

2026-08-30

HVTrust Changed

HVTrust up 6.2pts (49.9 → 56.1)

2026-08-29

Grade Changed

Trust grade C → D

2026-08-29

Rank Moved

Rank dropped 38 spots (#569 → #607)

2026-08-28

Rank Moved

Rank dropped 17 spots (#552 → #569)

2026-08-27

Rank Moved

Rank dropped 16 spots (#536 → #552)

2026-08-26

Rank Moved

Rank dropped 75 spots (#461 → #536)

2026-08-24

Rank Moved

Rank dropped 16 spots (#445 → #461)

2026-08-22

Rank Moved

Rank rose 14 spots (#460 → #446)

2026-08-19

Rank Moved

Rank dropped 13 spots (#447 → #460)

2026-08-17

Rank Moved

Rank rose 11 spots (#457 → #446)

2026-08-13

Rank Moved

Rank dropped 15 spots (#430 → #445)

2026-08-12

Rank Moved

Rank rose 15 spots (#445 → #430)

2026-08-10

Rank Moved

Rank dropped 17 spots (#424 → #441)

2026-08-08

Newly Listed

First tracked at rank #422

GitHub → PyPI: local-faiss-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/local-faiss-mcp-server.svg)](https://hvtracker.net/agents/local-faiss-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/local-faiss-mcp-server"><img src="https://hvtracker.net/badge/local-faiss-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON