| FMRS | 58 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 18 / 20 |
|---|
| Maintenance | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 8 / 20 | 15 / 20 |
|---|
| Best for | - Security teams to monitor company-wide agent supply chain risk
- Developers to quickly assess security of their MCP servers and skills
- Evaluating third-party MCP configs in sandboxed environments
| - 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 needing stable programmatic output (CLI output is experimental and may change)
- Production workflows depending on specific CLI output fields
- Scanning non-stdio MCP servers (only stdio is supported)
| - 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 SNYK_TOKEN environment variable to call Snyk API
- Executes commands defined in MCP configurations (stdio server startup)
- Reads local agent configuration files (e.g., ~/.claude/skills)
| - 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 | - Scanning MCP configurations executes their commands, posing risk of malicious code execution
- Skills, app names, and tool descriptions are shared with Snyk (usage implies consent)
- CLI output is experimental and subject to change
- Large-scale API usage may result in account blocking
| - 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 Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Amazon Q, Amp, Kiro, OpenCode, Antigravity, Codex, OpenClaw | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 0 | 0 |
|---|