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.
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 a mcp server in the Developer Tools section. It was first seen on 2026-06-26 and last updated 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 evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned kruschdev/krusch-context-mcp a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 66.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
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.