Is Local FAISS MCP Server safe to use?

Local FAISS MCP Server has an HVTrust score of 55.3/100 (Grade C), ranked #608 of 1320 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 55.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 33 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 Grade C Listed MIT

55.3/100

Rank #608 of 1320

Compare Local FAISS MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-04-24 · 133d ago

Recent change

Rank +11

Is Local FAISS MCP Server safe? Local FAISS MCP Server scores 55.3/100 (Grade C), ranked #608 of 1320 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 →

Ranked neighbours in MCP Servers

#290 Better Notion MCP — 55.5 (C) → #291 Obsidian Local REST API — 55.3 (C) → #293 Mistral MCP — 55.2 (C) → #294 SharePoint MCP Server — 55.2 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

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)

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 133 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

20.9

Activity sub-score · out of 100

#292

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-04

Activity & Reach

Stars

Forks

Last Push

2026-04-24

133 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼35

was #573

Analysis

HVTrust Dimensions vs MCP Servers

55.3 / 100 · 100.0% confidence

Local FAISS MCP Server MCP Servers average (778 agents)

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

12.1 / 25

2.5 above avg 9.6

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

0.8 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

3.1 / 20

9.1 below avg 12.2

AdoptionLog-scaled stars · package downloads

5.1 / 20

1.2 below avg 6.3

Activity Inputs

20.9 / 100

StarsRepository reach

9.2 / 30

FreshnessLast push recency

6.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Aug 30, 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

Is Local FAISS MCP Server safe?

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

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