Zero-config MCP server for searchable documentation. SQLite or PostgreSQL.
Stop pasting files into context. Your AI agent searches your local docs instead.5–10× fewer tokens per lookup. 92 % Hit@5 on real dev docs. Zero cloud dependencies. Ingest docs → Search with highlights → Stats overview → Serve to AI agents LLMs hallucinate API signatures that don't exist Entire files dumped into context — 3,000–15,000 tokens per doc Architecture decisions buried…
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”.
Stop pasting files into context. Your AI agent searches your local docs instead.5–10× fewer tokens per lookup. 92 % Hit@5 on real dev docs. Zero cloud dependencies. Ingest docs → Search with highlights → Stats overview → Serve to AI agents LLMs hallucinate API signatures that don't exist Entire files dumped into context — 3,000–15,000 tokens per doc Architecture decisions buried across dozens of files Every repeated lookup pays full context cost returns ranked, highlighted…
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.