WorkBuddy

Why scan WorkBuddy?

WorkBuddy loads MCP servers next to its extension surface, so a server entry and an extension can reach the same workspace while being reviewed by different people.

Usage

CallLint can auto-discover and scan WorkBuddy configurations:

calllint scan --agent workbuddy

How to start

Install nothing globally — run CallLint straight from npm:

npx calllint scan --auto

Then scan WorkBuddy specifically:

calllint scan --agent workbuddy

How to verify it worked

Confirm each server’s origin before acting on a SAFE verdict — SAFE means no blocker was observed under current evidence, not that the publisher was verified.

What CallLint does to WorkBuddy

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 WorkBuddy configurations in:

• ~/.workbuddy/mcp.json
• <project>/.workbuddy/mcp.json

Authority Surfaces

WorkBuddy can grant tools the following authority surfaces:

• mcp
• extensions

Distribution

CallLint is available for WorkBuddy through:

• mcp-stdio (via officialMcpRegistry) — Listing not yet verified
• tencent-mcp-market — Not available here
  ⚠️ Third-party MCP submissions not currently accepted

Support Status

Auto-detects — CallLint finds this host’s config on its own.

The commands under Usage are the ones CallLint actually supports for WorkBuddy today. Anything not listed there is not claimed.

Official Sources

• https://cloud.tencent.com/product/workbuddy