2 checks that ran failed — supply chain and version behavior — so this release can’t be trusted as-is.
- Publisher
- io.github.pvliesdonk
- Repository
- github.com/pvliesdonk/markdown-vault-mcp
- Install
- pypi:markdown-vault-mcp, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.13.3, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.13.4, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.14.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.15.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.16.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.17.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.18.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.18.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.19.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.19.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.20.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.20.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.21.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.22.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.22.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.23.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.23.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.25.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.27.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v1.27.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v3.0.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v3.0.1, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v3.0.2, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v3.0.3, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v3.0.4, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v3.1.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v4.0.0, pypi:markdown-vault-mcp, oci:ghcr.io/pvliesdonk/markdown-vault-mcp:v4.1.0
- Versions
- 29
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-09-04 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
fail25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
Python build script executes at build time: subprocess in build script, network call in build script
Credential hygiene
warn15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
tests/test_git.py: assigns a literal to secret (ghp_…yz (len 25)) — non-provider secret literal; prefer environment intake. tests/test_git.py: assigns a literal to secret (ghp_…23 (len 22)) — non-provider secret literal; prefer environment intake. tests/test_git.py: assigns a literal to secret (ghp_…99 (len 21)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. src/markdown_vault_mcp/cli.py) — the recommended intake shape.
Permission scope
warn15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
has both shell/exec and network egress — capable of download-and-run, though no such path was observed (src/markdown_vault_mcp/git.py: subprocess.* call; src/markdown_vault_mcp/providers.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (src/markdown_vault_mcp/git.py: subprocess.* call; src/markdown_vault_mcp/collection.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: src/markdown_vault_mcp/git.py: subprocess.* call discloses dynamic code execution: src/markdown_vault_mcp/_server_prompts.py: uses eval()/exec() discloses broad/destructive filesystem access: src/markdown_vault_mcp/collection.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: src/markdown_vault_mcp/collection.py: recursive glob ('**') from a broad root Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 4.0.0 (minor bump): new capability primitive(s) in source: child_process, fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): api.openai.com, auth.example.com, example.com, github.com, mcp.example.com, myhost, pvliesdonk.github.io, remote-host.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references tracking behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v4.1.0 · current | 2026-08-30 | D | 45 | 5/6 · 75% | B→D in v4.1.0 |
| v4.0.0 | 2026-08-25 | B | 75 | 4/6 · 65% | ±0 |
| v3.1.0 | 2026-07-08 | B | 80 | 4/6 · 65% | ±0 |
| v1.27.0 | 2026-04-21 | B | 75 | 3/6 · 55% | — |