Continue
CallLint support for Continue by Continue. CallLint does not auto-discover Continue configuration. A block file may live in .continue/mcpServers as YAML or as JSON copied from another host, so a deterministic extractor must read both shapes before this page can promise more than where the config lives.
Why scan Continue?
Continue holds MCP servers as tools inside the editor, and a server block can arrive as YAML or as JSON copied from another host — two shapes, one authority grant.
Usage
CallLint does not yet support native auto-discovery for Continue. No automatic detection yet — this page documents where the config lives.
What CallLint does to Continue
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 Continue configurations in:
<project>/.continue/mcpServers/*.yaml<project>/.continue/mcpServers/*.jsonconfig.yaml mcpServers block
Distribution
CallLint is available for Continue through:
- mcp-stdio (via officialMcpRegistry) — Listing not yet verified
Support Status
Guide only — No automatic detection yet — this page documents where the config lives.
CallLint publishes no scan command for Continue yet. That is a statement about CallLint's coverage, not about Continue: see Coverage Boundary for what would have to be built first.
Official Sources
Coverage Boundary
CallLint does not auto-discover Continue configuration. A block file may live in .continue/mcpServers as YAML or as JSON copied from another host, so a deterministic extractor must read both shapes before this page can promise more than where the config lives.