Show HN: Knowerage – code coverage for LLM analysis
Knowerage is a tool designed for code coverage analysis in AI applications. It allows users to analyze and document code without needing to memorize tool names, providing insights into code coverage and gaps. The tool integrates with various MCP servers and offers functionalities for creating and updating analysis documents.
- ▪Knowerage requires Node.js 18 or newer and can be configured with MCP servers using specific JSON formats.
- ▪Users can analyze code by simply pointing to files or classes, and the tool generates markdown files for documentation.
- ▪The registry tracks analysis records and coverage, allowing users to query how much of the code has been analyzed.
Hacker News (Front Page) files mainly under programming. We currently carry 724 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/MTimma/knowerage |
| Publication time | Tue, 28 Apr 2026 12:36:24 +0000 |
| Retrieval time | 2026-04-28T12:49:31.928Z |
| Last seen | 2026-04-28T12:49:31.928Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 8Jz7fgVyMjBj |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Knowerage — AI Analysis Coverage Management Links: GitHub · Glama MCP listing · npm @mtimma/knowerage Quick Start Requirements: Node.js 18 or newer — npx must be on your PATH (it comes with npm, which is included with Node). MCP server configuration Register Knowerage wherever your MCP host expects server definitions (for example some clients use .cursor/mcp.json or .vscode/mcp.json; others use environment variables or a UI—follow your host’s documentation). Use the same server entry shape: { "mcpServers": { "knowerage": { "command": "npx", "args": ["@mtimma/knowerage"], "env": { "KNOWERAGE_WORKSPACE_ROOT": "${workspaceFolder}", "KNOWERAGE_AUTO_FULL_RECONCILE": "true" } } } } Replace ${workspaceFolder} with your project root if your host does not expand that variable.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.