Section-level doc search for .md, .rst, .adoc, .ipynb, .html, .yaml, .json, and OpenAPI specs.
Most AI agents still explore documentation the expensive way: open file → skim hundreds of irrelevant paragraphs → open another file → repeat That burns tokens, floods context windows with noise, and forces models to reason through a lot of text they never needed in the first place. jDocMunch-MCP lets AI agents navigate documentation by section instead of reading files by brute force. It indexes…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Most AI agents still explore documentation the expensive way: open file → skim hundreds of irrelevant paragraphs → open another file → repeat That burns tokens, floods context windows with noise, and forces models to reason through a lot of text they never needed in the first place. jDocMunch-MCP lets AI agents navigate documentation by section instead of reading files by brute force. It indexes a documentation set once, then retrieves exactly the section the agent actually needs, with…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.