| FMRS | 64 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 14 / 20 | 18 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - AI agents and developers conducting evidence-first code research.
- Teams analyzing both local workspaces and GitHub repositories.
- Code review, refactoring, and architecture work requiring semantic navigation, structural search, and compact context.
| - 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 seeking browser automation, cloud storage, collaboration, or database operations.
- Environments that cannot grant local workspace or GitHub access.
- Clients requiring a transport other than stdio.
| - 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 | - Local tools can access paths permitted by configuration; local tools are enabled by default.
- GitHub tools require GitHub authentication; personal access tokens support repo, read:user, and read:org scopes.
- When cloning is enabled, the server accesses GitHub repositories and uses a local cache.
| - 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 | - Local tools may read code and files within permitted paths; the server blocks many sensitive files and directories.
- GitHub tokens are sensitive credentials and should be supplied through environment variables or secure credential management, never committed to version control.
- Secret scanning and automatic redaction may reduce returned-content completeness.
- Enabling repository cloning expands local caching and external repository data handling.
| - 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 | Cursor, VS Code, VS Code Insiders, Windsurf, Kiro, Goose, LM Studio, Claude Code | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 12 | 0 |
|---|