MCP100 IndexFiles & Knowledge
MCP100 SelectedCommunity implementation

Codebase Memory

by io.github.DeusData

Updated August 14, 2026 · Reviewed August 11, 2026

Files & KnowledgeSoftware & Technology

MCP100 verdict

Recommended for repeated structural exploration of medium or large local repositories where a persistent code knowledge graph saves context and search time.

MCP100 Assessment

Editorial verdict

Recommended for repeated structural exploration of medium or large local repositories where a persistent code knowledge graph saves context and search time.

Reviewed 2026-08-11 · Next review 2026-09-10

Task Fit

Mapped

Local files and knowledge

Trust

Reviewed

A dated editorial review is published on the MCP detail page.

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

  • Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages

Not ideal for

  • Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers

Avoid if

  • The source tree cannot be indexed locally or persistent cache files are prohibited

Trade-offs

  • Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed.

Evidence scope

Evidence

Current source snapshot

Popularity

38.9k MCP repository stars

28k 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-14T18:07:21Z

Current source snapshot

Trust review

Source relationship: Community implementation

Reviewed 2026-08-11 · Next review 2026-09-10