Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for coding-agent users who want persistent local project context without pushing code search and project memory into a hosted service.
Where this stands now
kruschdev/krusch-context-mcp ranks #118 of 1270 tracked Developer Tools items by composite score (7.9 against a section median of 4.9). The section currently carries 1032 Bronze, 134 Silver, 103 Gold, 1 Low Signal. RepoRadar has retained observations for this record since 2026-06-26 (99 days in the current window). Signal extremes versus the section: momentum at the 90th percentile; novelty at the 89th percentile.
Who should use it
Who should skip it
Skip kruschdev/krusch-context-mcp if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
kruschdev/krusch-context-mcp is tracked by RepoRadar as an MCP server in the Developer Tools section. First seen 2026-06-26; the source record was last checked on 2026-06-26. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for kruschdev/krusch-context-mcp are workflow potential (9.4) and open-source/build quality (8.4), while momentum (6.0) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The kruschdev/krusch-context-mcp record combines a 7.9/10 composite score with separate popularity (66.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The system stores code-derived context and project memory locally, so review the database and note contents before indexing sensitive repositories; Setup depends on local Postgres, SQLite, and Ollama components, which adds operational complexity compared with a single-binary MCP server; Memory and deep-search retrieval can surface stale or overconfident past context, so keep a human in the loop for important code decisions.