Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Markdown Vault MCP

OCI · GHCR.IO/PVLIESDONK/MARKDOWN-VAULT-MCP · 2 COMPONENTS

Generic markdown vault MCP with hybrid search

Available components

oci · ghcr.io/pvliesdonk/markdown-vault-mcp 21 pypi · markdown-vault-mcp 35
+21 this week 21 Trust /100

Last scanned (9 hours ago)

Scores higher than 35% of OCI servers

Category Memory and Knowledge

Recent critical change

CVE-2026-114615 affects this package (31 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security2
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pvliesdonk/markdown-vault-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • CVE-2026-109518 affects this package: none ▼ security
  • 2 Nov 26 0
    • Package version: v6.0.0 → v6.1.0 functional
  • 1 Nov 26 +21
    • RUSTSEC-2026-0385 affects this package: none ▼ security
    • CVE-2026-76642 affects this package: none ▼ security
    • RUSTSEC-2026-0221 affects this package: none ▼ security
    • CVE-2026-53910 affects this package: none ▼ security
    • CVE-2026-114615 no longer affects this package ▲ security
    • CVE-2026-114616 no longer affects this package ▲ security
    • CVE-2026-96760 no longer affects this package ▲ security
    • GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Known CVEs: CVE check failed: a known advisory affects this package; its severity couldn't be graded. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Score status: failed → scored ▲ functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: v5.1.0 → v6.0.0 functional
  • 31 Oct 26 0
    • CVE-2026-114615 affects this package: high ▼ critical
    • CVE-2026-114616 affects this package: high ▼ critical
  • 28 Oct 26 0
    • CVE-2026-96760 affects this package: high ▼ critical
  • 21 Oct 26 −21
    • GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
    • Score status: scored → failed ▼ critical
    • Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
    • CVE-2026-76642 no longer affects this package ▲ security
    • RUSTSEC-2026-0221 no longer affects this package ▲ security
    • RUSTSEC-2026-0258 no longer affects this package ▲ security
    • CVE-2026-53910 no longer affects this package ▲ security
  • 14 Oct 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
  • 9 Oct 26 21

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/pvliesdonk/markdown-vault-mcp@v6.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via OCI referrers API
Source repo pvliesdonk/markdown-vault-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pvliesdonk/markdown-vault-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 3649228464
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:e69a1be212d8ed9df010c1975ee3958b6264794f87e231858b6281ab7c0ec302

Background: How many MCP packages publish verified provenance →

Vulnerabilities 25 findings
ID CVE Severity Vector Fix available
DEBIAN-CVE-2011-3374 CVE-2011-3374 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-109518 CVE-2026-109518 none yes
DEBIAN-CVE-2022-0563 CVE-2022-0563 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2026-3184 CVE-2026-3184 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-76642 CVE-2026-76642 none no
DEBIAN-CVE-2026-78408 CVE-2026-78408 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H no
DEBIAN-CVE-2026-78409 CVE-2026-78409 high CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2026-78410 CVE-2026-78410 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2017-18018 CVE-2017-18018 medium CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N no
DEBIAN-CVE-2025-5278 CVE-2025-5278 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L no
DEBIAN-CVE-2026-56391 CVE-2026-56391 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H no
DEBIAN-CVE-2026-56392 CVE-2026-56392 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H no
RUSTSEC-2026-0385 none yes
DEBIAN-CVE-2026-102473 CVE-2026-102473 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-102474 CVE-2026-102474 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-53910 CVE-2026-53910 none no
RUSTSEC-2026-0221 none yes
DEBIAN-CVE-2026-102010 CVE-2026-102010 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H no
DEBIAN-CVE-2026-114690 CVE-2026-114690 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-114691 CVE-2026-114691 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-115455 CVE-2026-115455 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H no
DEBIAN-CVE-2026-95619 CVE-2026-95619 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H no
DEBIAN-CVE-2018-1000021 CVE-2018-1000021 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L no
DEBIAN-CVE-2022-24975 CVE-2022-24975 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2024-52005 CVE-2024-52005 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H no

Background: What a vulnerability scan can and cannot prove →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/pvliesdonk/markdown-vault-mcp

# install command
$ docker pull ghcr.io/pvliesdonk/markdown-vault-mcp:v6.1.0
Common questions

What is the Markdown Vault MCP server?

Markdown Vault MCP is listed in the public MCP registry as io.github.pvliesdonk/markdown-vault-mcp. Generic markdown vault MCP with hybrid search. This page covers its container image (ghcr.io/pvliesdonk/markdown-vault-mcp).

Is the Markdown Vault MCP server safe to use?

Markdown Vault MCP scores 21 out of 100 on VerifyMCP. We recorded 25 known advisories against it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Markdown Vault MCP server still maintained?

Markdown Vault MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Markdown Vault MCP server under?

Markdown Vault MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.