Markdown Vault MCP

Generic markdown collection MCP server with FTS5 + semantic search, frontmatter-aware indexing, and incremental reindexi

MCP Servers Python Grade A Listed MIT
82.8/100
Rank #72 of 1320
Compare Markdown Vault MCP

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank

Is Markdown Vault MCP safe? Markdown Vault MCP scores 82.8/100 (Grade A), ranked #72 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 5.8/10; 98% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-08-31
Rank Moved
Rank dropped 11 spots (#72 → #83)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.8/10
2026-08-26
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
64.6
Activity sub-score · out of 100
#20

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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-09-04 14:03 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
32
Forks
14
Last Push
2026-09-04
today
Commits (4 wk)
163
Downloads (7d)
746
pypi
HN mentions (30d)
Open Issues
40
Rank Change
▼1
was #71

Analysis

HVTrust Dimensions vs MCP Servers

82.8 / 100 · 100.0% confidence

Markdown Vault MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.7 / 25
10.2 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
1.6 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.5 / 20
1.3 above avg 6.2

Activity Inputs

64.6 / 100
StarsRepository reach
9.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
5.5 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.8 / 10
OpenSSF Scorecard · scanned Aug 26, 2026
Signed Commits
98%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 4
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 10
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 10

Is Markdown Vault MCP safe?

Public supply-chain signals for Markdown Vault MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Markdown Vault MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Markdown Vault MCP publish package provenance?
Yes. Markdown Vault MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Markdown Vault MCP have an OpenSSF Scorecard?
Markdown Vault MCP has an OpenSSF Scorecard score of 5.8/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 Markdown Vault MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Markdown Vault MCP use?
Markdown Vault MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Markdown Vault MCP's commits signed?
98% of the last 100 commits to Markdown Vault MCP 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
Markdown Vault MCP 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
Declared
Declared plugin/integration 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 Markdown Vault MCP?

For maintainers

HVTrust scores Markdown Vault MCP 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 8Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-31
Rank Moved
Rank dropped 11 spots (#72 → #83)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.8/10
2026-08-26
Grade Changed
Trust grade B → A
2026-08-26
Rank Moved
Rank rose 81 spots (#151 → #70)
2026-08-26
HVTrust Changed
HVTrust up 12.1pts (69.7 → 81.8)
2026-08-24
Rank Moved
Rank dropped 11 spots (#140 → #151)
2026-08-22
Rank Moved
Rank rose 11 spots (#152 → #141)
2026-08-17
Rank Moved
Rank rose 10 spots (#158 → #148)
2026-08-13
Rank Moved
Rank dropped 12 spots (#144 → #156)
2026-08-12
Rank Moved
Rank rose 12 spots (#156 → #144)
2026-08-10
Rank Moved
Rank dropped 12 spots (#155 → #167)
2026-08-08
Newly Listed
First tracked at rank #154

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 82.8 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/markdown-vault-mcp.svg)](https://hvtracker.net/agents/markdown-vault-mcp)
HTML:
<a href="https://hvtracker.net/agents/markdown-vault-mcp"><img src="https://hvtracker.net/badge/markdown-vault-mcp.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