CodeBuddy
CallLint support for CodeBuddy by Tencent. CallLint does not yet support CodeBuddy native discovery.
Why scan CodeBuddy?
CodeBuddy loads MCP servers alongside its extension surface, so a server entry can reach the workspace an extension already trusts.
Usage
CallLint does not yet support native auto-discovery for CodeBuddy. Support is not implemented yet — this page documents what we can observe today.
What CallLint does to CodeBuddy
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 CodeBuddy configurations in:
Config path requires verification
Distribution
CallLint is available for CodeBuddy through:
- mcp-stdio (via officialMcpRegistry) — Listing not yet verified
-
tencent-mcp-market
— Not available here
⚠️ Third-party MCP submissions not currently accepted
Support Status
Guide only — Support is not implemented yet — this page documents what we can observe today.
CallLint publishes no scan command for CodeBuddy yet. That is a statement about CallLint's coverage, not about CodeBuddy: see Coverage Boundary for what would have to be built first.
Official Sources
Coverage Boundary
CallLint does not yet support CodeBuddy native discovery.