MCP100 IndexMCP Server
WatchlistCommunity implementation

Drift

by dadbodgeoff

Reviewed October 5, 2026

MCP ServerSoftware & Technology

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow the beta CLI and MCP fingerprint behavior as the project matures

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Codebase convention intelligence and durable coding-agent memory

What we know

Local codebase-intelligence system that detects patterns/conventions and exposes context plus persistent memory to coding agents over MCP.

Maintenance / activity evidence

  • Observed (UTC)Merge pull request 139 from dadbodgeoff/remediation/binding-alias-la…

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Reads source repository and writes local intelligence/memory state. Writes: Store/update memory; Generate local analysis state.
  • Authentication not yet verified.
  • Sensitive access: Source code, Engineering decisions
  • Local-first operation limits network exposure but persistently indexes source and conventions.
Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

790 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Does Drift's read-only MCP surface still expose reproducible repository findings?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

  • Local-first operation limits network exposure but persistently indexes source and conventions.
  • Reads source repository and writes local intelligence/memory state.
  • Runs entirely on the user's machine per project docs.
  • Reviewed write actions: Store/update memory; Generate local analysis state
  • Sensitive access: Source code, Engineering decisions
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • No independent runtime, installation, or comprehensive security audit was performed.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • Current beta installs from source; unrelated npm packages must not be used.
  • Memory and codebase analysis are persistent.

Original activity observations

  • 2026-08-20T07:03:29Z: Merge pull request 139 from dadbodgeoff/remediation/binding-alias-la…
Technical identity
github.com/dadbodgeoff/drift
Exact implementation source
https://github.com/dadbodgeoff/drift ↗
Reviewed resource type
MCP Server
Repository identity
dadbodgeoff/drift

Evidence & Sources

Evidence basis
Recorded source evidence
Setup runtime verification
Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed · Latest source observation

  • GitHub repository ↗

    dadbodgeoff/drift

    Recorded repository material and project history.

    Includes references whose attribution is not established.