OpenCode
CallLint support for OpenCode by Open Source. CallLint scans local and remote servers under the root mcp key. {env:VAR} placeholders are recorded unresolved, never expanded against the host environment.
Why scan OpenCode?
OpenCode reaches MCP servers as tools, and its launch spec is a single command array under the root `mcp` key — one entry grants local execution authority with its own environment.
Usage
CallLint can auto-discover and scan OpenCode configurations:
calllint scan --agent opencodeHow to start
Install nothing globally — run CallLint straight from npm:
npx calllint scan --autoThen scan OpenCode specifically:
calllint scan --agent opencodeHow to verify it worked
Look at what the command array resolves to. OpenCode writes the executable and its arguments as one list, so a local script and a pinned package look alike until the verdict separates them.
What CallLint does to OpenCode
Offline by default. Deterministic. Never executes the server it judges. SAFE means no blockers observed, not a proof of runtime safety.
A No blockers observed verdict means exactly that — no blocker under the evidence CallLint could collect. It is not a guarantee, and Insufficient evidence never becomes it on its own. See Coverage Boundary for what this scan does not look at.
Configuration Paths
CallLint looks for OpenCode configurations in:
~/.config/opencode/opencode.json<project>/opencode.json<project>/opencode.jsonc
Distribution
CallLint is available for OpenCode through:
- mcp-stdio (via officialMcpRegistry) — Listing not yet verified
Support Status
Auto-detects — CallLint finds this host’s config on its own.
The commands under Usage are the ones CallLint actually supports for OpenCode today. Anything not listed there is not claimed.
Official Sources
Coverage Boundary
CallLint scans local and remote servers under the root mcp key. {env:VAR} placeholders are recorded unresolved, never expanded against the host environment.