MCP100 verdict
Not currently recommended. Build and query a semantic graph of a software codebase.
MCP100 Assessment
Editorial verdict
Build and query a semantic graph of a software codebase.
Reviewed 2026-07-24 · Next review 2026-10-24
Task Fit
Mapped
Developer workflows
Trust
Status warning
tool_contract; install_supply_chain; advisory_freshness
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Exploring callers, callees, imports, dependencies, and change impact
- Large multilingual repositories where graph relationships add value beyond text search
- Teams wanting local code indexing without an external API key
Not ideal for
- Small repositories adequately served by native code search
- Memory-constrained environments that cannot support the default embedding model
- Repositories whose source-derived indexes may not be persisted locally
Avoid if
- Source code cannot be indexed into a local persistent database
- The MCP process may start in an unintended working directory
- Generated, private, or credential-bearing paths cannot be excluded
Trade-offs
- Semantic graphs provide relationship-aware context but indexing consumes local CPU, memory, and storage.
- Graph-only and narrow tool profiles reduce resource and context cost but remove semantic or broader tool capabilities.
- Community features are open source, while additional Pro analysis and security capabilities are separately offered.
Evidence scope
Evidence
Popularity
61 MCP repository stars
5.5k package downloads
Stars observed 2026-08-14T18:46:26.000Z · Downloads observed 2026-08-14T18:46:26.000Z
Exact implementation repository metric.
Exact implementation package metric.
Maintenance
Publisher activity observed 2026-08-10T02:23:34Z
Current source snapshot
Trust review
Source relationship: First-party MCP
Reviewed 2026-07-24 · Next review 2026-10-24