Skip to content

Security: Flopsstuff/markdown-vault-mcp

Security

SECURITY.md

Security policy

Reporting a vulnerability

Report it privately through GitHub: open Security → Report a vulnerability on this repository, or go straight to https://github.com/pvliesdonk/markdown-vault-mcp/security/advisories/new. That opens a draft security advisory only you and the maintainers can read.

Before reporting, read docs/security-model.md. It states what the server protects and what it leaves to the operator.

Do not open a public issue, pull request or discussion for a suspected vulnerability. If the reporting form is unavailable, open an issue titled "Security contact request" that says nothing about the finding itself, and a maintainer replies with a private channel.

Include what you can of:

  • the affected artifact and version: package version, image tag, or commit;
  • the tool, resource, prompt, endpoint or configuration involved;
  • steps or a proof of concept that reproduces it;
  • the impact you believe it has, and who can trigger it.

Response targets and scope

The maintainers aim to:

  • acknowledge a report within 7 days;
  • assess it and share the planned fix, or the reason it is not treated as a vulnerability, within 30 days;
  • publish the fix and the advisory together, within 90 days of the report or sooner, and coordinate the date with the reporter.

In scope: this server as shipped from this repository, its Python package, its container image, its Linux packages and its Claude Desktop bundle.

Out of scope: findings that require an already-compromised host, denial of service by resource exhaustion from an authenticated client, and reports generated by automated scanners without a demonstrated impact.

Supported versions

Version Supported
The latest stable release (vX.Y.Z) Yes
The latest patch on an open release/X.Y branch Yes, while the branch is open
Pre-releases (vX.Y.Z-rc.N) and the rolling edge build Reports are welcome; the fix ships in the next stable release
Older stable releases No, upgrade to the latest release

A fix ships as a new release on the stable channel. See the release process in docs/contribute/release-process.md for how a patch reaches an open release/X.Y branch.

Where a fix lands

This project is generated from fastmcp-server-template on top of the fastmcp-pvl-core library. Report here regardless of where the flaw sits; the maintainers route it. A flaw in a template-owned file or in the library is fixed upstream and reaches this project through a template update or a dependency bump, and the advisory here links the upstream one.

Disclosure and credit

Disclosure is coordinated: the advisory is published when a fix is available, or at the agreed date if the reporter and the maintainers settle on one. The advisory credits the reporter unless they ask otherwise. There is no bounty programme.

There aren't any published security advisories