CallLint

Agent Harnesses

CallLint provides deterministic static preflight inspection for agent hosts and development environments that can execute MCP servers and agent tools.

Supported Hosts

CallLint tracks 18 agent harnesses: 13 with native auto-discovery (--agent <id>), 5 documented only, with no detection yet.

P0/P1/P2-P3 order these hosts by how commonly they are used, not by how well CallLint supports them. Each host below carries its own support label.

Native Support (P0)

  • Claude Code by Anthropic Auto-detects
    CallLint scans MCP server entries only. Skills, hooks and permission settings in the same file are not covered.
  • Claude Desktop by Anthropic Auto-detects
    CallLint scans MCP server entries only. Other Claude Desktop settings in the same file are not covered.
  • Cursor by Anysphere Auto-detects
    CallLint scans MCP server entries only. Cursor rules and editor settings are not covered. Cloud Agents, background agents, cloud subscriptions and event or timer wakeups (GitHub, Slack, Linear, cron) are not statically observable at all: what starts such an agent is decided in Cursor's cloud, not in a file on disk, so CallLint reports that authority as UNSUPPORTED rather than reading it as SAFE. The same holds for where a Cloud Agent runs and for what it changes when it is done. A Cloud Agent can start with no repository at all and run in a Cursor-managed cloud environment, so there is no config file to read the run out of; and its results can create or change a Cursor Origin repository, expose the live environment to a browser through port forwarding, or publish through a connected Vercel account. None of that leaves deterministic static evidence on this machine, so all of it is UNSUPPORTED too. Reading Cursor's MCP config tells you what one layer of Cursor's authority declares, never that the layers CallLint cannot see are safe.
  • WorkBuddy by Tencent Cloud Auto-detects
    CallLint scans MCP server entries only. Other WorkBuddy settings in the same file are not covered.

Additional Support (P1)

Config-Scan or Discovery-Only (P2-P3)

Official MCP Registry

CallLint is published to the Official MCP Registry as io.github.calllint/calllint (package: calllint-mcp).

Platforms that consume the Official MCP Registry can discover CallLint automatically.

Registry Consumption Audit (G3.5)

Supporting MCP stdio is not the same as consuming the Official Registry. A platform's distribution primitive is marked AVAILABLE only where Registry consumption has been confirmed; everything still unverified carries AUDIT_REQUIRED.

Audit state across the 18 tracked hosts, counted from the distribution source of truth:

  • BLOCKED — 1 primitive(s)

View full audit: platform-audit-G3.md