← Case index
Case file No.438 · pypi · stdio
jDocmunch MCP
io.github.jgravelle/jdocmunch-mcp · v1.150.0
Section-level doc search for .md, .rst, .adoc, .ipynb, .html, .yaml, .json, and OpenAPI specs.
Security score
91/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- v1.149.0 → v1.150.0Oct 21, 2026
versionchanged version bump"1.149.0" → "1.150.0"
packages.0.versionchanged package version bump"1.149.0" → "1.150.0"
- v1.148.0 → v1.149.0Oct 19, 2026
versionchanged version bump"1.148.0" → "1.149.0"
packages.0.versionchanged package version bump"1.148.0" → "1.149.0"
- v1.147.1 → v1.148.0Oct 18, 2026
versionchanged version bump"1.147.1" → "1.148.0"
packages.0.versionchanged package version bump"1.147.1" → "1.148.0"
- First snapshot (v1.147.1)Oct 17, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs jDocmunch MCP safe?
MCPWatch gives jDocmunch MCP a heuristic security score of 91/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does jDocmunch MCP have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package jdocmunch-mcp. That is not proof of safety.
When was jDocmunch MCP last updated?
The latest registry version is 1.150.0, published Oct 20, 2026. The last push to jgravelle/jdocmunch-mcp was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.
What license does jDocmunch MCP use?
GitHub did not detect a license for jgravelle/jdocmunch-mcp.