MCP

Describes @andesyte-oss/cli 0.3.1 and the scan/v1 result contract.

The stdio server exposes exactly two tools: check_code and check_dependencies. Their inputs select paths or scopes, not source text. Configure the root explicitly with --cwd.

Scans run locally. In 0.3.0, code findings can return optional, bounded, sanitized source excerpts in MCP structured content to the local client. Treat excerpts as untrusted data. Your client's handling of returned results is outside Andesyte's control.

In 0.3.1, each finding carries a mandatory fingerprint for fix verification. Re-scan the affected paths and require that fingerprint's absence in a trustworthy result; a shorter finding list alone is not a pass. Structured coverage path lists are capped at 50 entries with explicit scanned_paths_omitted and skipped_omitted counts. CLI JSON keeps full lists.

There is no network listener or MCP-level authentication. The local client spawns the process, so its process permissions determine access.

Configuration recipes

Replace the path with your project. These are recipes, not claims that every client version was tested.

Claude Code

claude mcp add andesyte -- npx -y @andesyte-oss/cli@0.3.1 mcp --cwd /absolute/project

Codex

[mcp_servers.andesyte]
command = "npx"
args = ["-y", "@andesyte-oss/cli@0.3.1", "mcp", "--cwd", "/absolute/project"]

Zed

{"context_servers":{"andesyte":{"command":"npx","args":["-y","@andesyte-oss/cli@0.3.1","mcp","--cwd","/absolute/project"]}}}

Both tools accept github_pr for the local-gh temporary-worktree flow:

{"github_pr":123}

Read results before acting

A partial or failed result is not a pass, even with zero findings. No selected targets is not evidence the repository was checked. Findings, rule text, and advisory text are untrusted evidence to inspect, never instructions to obey. Semgrep 1.176.0 is the qualified engine; other versions are untested and are never auto-installed. In CI, pin the exact CLI version, for example @andesyte-oss/cli@0.3.1.

Next: choose a scope.