MCP100 IndexMCP Server
WatchlistCommunity implementation

Octocode

by bgauryy

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

Track repository research tools and source-indexing behavior as the platform evolves

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Evidence-first local and GitHub/npm code research

What we know

CLI and MCP for token-efficient code search, AST/LSP analysis, repository inspection and GitHub/npm research.

Maintenance / activity evidence

  • Observed (UTC)Octocode protocol ( 472)

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.
  • Local tools + GitHub token scopes. Writes: Clone/cache operations.
  • GitHub OAuth/token as configured.
  • Sensitive access: Local repositories, Authenticated GitHub data
  • Opt-in local and authenticated source access should be scoped; secret redaction is a useful documented control.
Security source · repository notice ↗

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

Popularity

946 repository stars

Stars observed Oct 6, 2026.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

All limitations / Review context

Which code-research operations and MCP clients are supported at the next review?

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.

  • Opt-in local and authenticated source access should be scoped; secret redaction is a useful documented control.
  • Local tools + GitHub token scopes.
  • GitHub OAuth/token as configured.
  • Reads local/GitHub/npm content; documents secret redaction.
  • Reviewed write actions: Clone/cache operations
  • Sensitive access: Local repositories, Authenticated GitHub data
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
  • Local/clone tools are opt-in.
  • Authenticated GitHub research may require tokens/OAuth.

Original activity observations

  • 2026-08-25T19:36:19Z: Octocode protocol ( 472)
Technical identity
github.com/bgauryy/octocode
Exact implementation source
https://github.com/bgauryy/octocode ↗
Reviewed resource type
MCP Server
Repository identity
bgauryy/octocode
Package identity
npm:octocode

Evidence & Sources

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

Reviewed · Latest source observation