| FMRS | 54 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 18 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Developers analyzing large or unfamiliar repositories
- Engineering teams using Claude Code, Cursor, or another MCP client
- Users who prioritize local indexing, targeted retrieval, and token-cost control
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Users who only need general chat or web browsing
- Environments that cannot or do not want to create local code indexes
- Enterprise buyers requiring an official product-owner-maintained server or a clearly declared open-source license
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Requires read access to local code directories or GitHub repositories being indexed.
- Requires local write access for indexes and session data, stored by default under ~/.code-index/ and configurable with CODE_INDEX_PATH.
- File watching, agent hooks, and login-service features require additional local configuration or service permissions when enabled.
- Anonymous token-savings telemetry may be sent to the project's public meter; it can be disabled with share_savings or JCODEMUNCH_SHARE_SAVINGS=0.
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - Indexed source and session data are stored locally; the session journal records paths and query strings touched during a session.
- Telemetry, AI summaries, embedding-model downloads, license validation, and Starter Pack operations can create outbound network requests when enabled or explicitly invoked.
- Some optional extras can access a microphone or process images; these are not core MCP server functionality.
- The README states that non-commercial personal use is free and commercial use requires a paid license; repository metadata lists the license as NOASSERTION.
- Token savings and retrieval quality depend on index coverage, language support, and query quality and are not unconditional guarantees.
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Claude Code, Cursor, VS Code, Codex, Continue, Windsurf, Autohand Code, Claude Desktop | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 13 | 0 |
|---|