Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow index and check coverage as the analysis engine evolves
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Codebase graph/context intelligence for review, refactor, debug and change-safety workflows.
What we know
Local code-intelligence CLI/MCP with graph indexing, impact analysis and selectable task-specific tool presets.
Maintenance / activity evidence
- Observed (UTC)fix(W805-EEEEE): update sister cross-check for W805-CCCCC fix lockstep
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Primarily local code-index/read analysis. Writes: Write/update local index metadata.
- Authentication not yet verified.
- Sensitive access: Source code
- Primarily read/analysis oriented; main risk is exposing source context to the connected model.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
518 repository stars
Stars observed Sep 25, 2026.
Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.
Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.
All limitations / Review context
Which code-index, finding, and MCP-facing check operations remain reproducible?
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.
- Primarily read/analysis oriented; main risk is exposing source context to the connected model.
- Primarily local code-index/read analysis.
- Indexes source locally; no external service requirement established.
- Reviewed write actions: Write/update local index metadata
- Sensitive access: Source code
- 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.
- Results can be partial/stale and must be checked for errors/scope/freshness.
- The meta-tool reports available presets but does not hot-switch the running server.
Original activity observations
- 2026-10-03T09:02:36Z: fix(W805-EEEEE): update sister cross-check for W805-CCCCC fix lockstep
Technical identity
github.com/cranot/roam-code- Exact implementation source
- https://github.com/cranot/roam-code ↗
- Reviewed resource type
- MCP Server
- Repository identity
- cranot/roam-code
- Package identity
- pypi:roam-code
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 ↗
cranot/roam-code
Recorded repository material and project history.
Includes references whose attribution is not established.
Setup · Watchlist
Install & Agents
Codex
Publisher instructions with a documented client setup path.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsPublisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions · Review before use
pip install "roam-code[mcp]" roam init roam mcp-setup codex-cli --writeConfigure / authenticate
Publisher instructionsRun inside project root. Alternative `codex mcp add roam-code -- roam mcp`. Ordinary analysis is local with no key.
Check connection
Publisher instructions`roam mcp --list-tools`; then `codex mcp list` and a read-only Roam query.
read only check · Publisher instructions
roam healthRemove / uninstall / revoke
MCP100 setup guide`codex mcp remove roam-code` removes Codex registration. Optional pip uninstall only if retiring the CLI.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
codex mcp remove roam-code
What it does
Local code-intelligence CLI/MCP with graph indexing, impact analysis and selectable task-specific tool presets.
- Capability
- Developer Tools
- Resource type
- MCP Server
- Best fit
- Codebase graph/context intelligence for review, refactor, debug and change-safety workflows.
Representative uses
- Build/query code graph
- Review impact of changes
- Support refactor/debug/architecture tasks
- Use 8 selectable MCP presets
Limitations
- Results can be partial/stale and must be checked for errors/scope/freshness.
- The meta-tool reports available presets but does not hot-switch the running server.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Not documented in the reviewed sources
- Permissions
- Primarily local code-index/read analysis.
- Data handling
- Indexes source locally; no external service requirement established.
- Cost
- free
- Risk and cautions
- Primarily read/analysis oriented; main risk is exposing source context to the connected model.
Access scope and cautions
- Write actions
- Write/update local index metadata
- Sensitive access
- Source code
- Risk level
- low
FAQ
Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What setup information is documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
Cranot is listed as Community implementation in MCP100’s current evidence.