Roo Code
CallLint support for Roo Code by Roo Code Inc. CallLint does not support Roo Code discovery. Its upstream repository is archived, so config evidence was not collected: recording a config path from a possibly-discontinued product would assert a state nobody has verified.
Why scan Roo Code?
Roo Code reaches MCP servers as tools from a VS Code extension, so a server entry is callable with whatever the extension can already reach.
Usage
CallLint does not yet support native auto-discovery for Roo Code. Support is not implemented yet — this page documents what we can observe today.
What CallLint does to Roo Code
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 Roo Code configurations in:
Config mechanism requires verification
Distribution
CallLint is available for Roo Code through:
- mcp-stdio (via officialMcpRegistry) — Awaiting the upstream registry
Support Status
Guide only — Support is not implemented yet — this page documents what we can observe today.
CallLint publishes no scan command for Roo Code yet. That is a statement about CallLint's coverage, not about Roo Code: see Coverage Boundary for what would have to be built first.
Official Sources
Coverage Boundary
CallLint does not support Roo Code discovery. Its upstream repository is archived, so config evidence was not collected: recording a config path from a possibly-discontinued product would assert a state nobody has verified.