Claude Code

Why scan Claude Code?

Claude Code grants an MCP server the same shell, filesystem and plugin reach the agent itself has, and its settings file is shared with skills and hooks — so one unreviewed server entry inherits the whole working directory.

Usage

CallLint can auto-discover and scan Claude Code configurations:

calllint scan --agent claude-code

How to start

Install nothing globally — run CallLint straight from npm:

npx calllint scan --auto

Then scan Claude Code specifically:

calllint scan --agent claude-code

How to verify it worked

Read the verdict line for each server. Anything not SAFE names the evidence that produced it, so the next step is to open that server’s command and confirm the authority it asks for is authority you meant to grant.

What CallLint does to Claude 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 Claude Code configurations in:

• ~/.claude/settings.json
• <project>/.claude/settings.json

Authority Surfaces

Claude Code can grant tools the following authority surfaces:

• mcp
• filesystem
• shell
• plugins

Distribution

CallLint is available for Claude Code through:

• mcp-stdio (via officialMcpRegistry) — Available now
• claude-plugin — Available now
  Claude Code has no marketplace to submit to: distribution is users adding this repo as a marketplace, so the act is publishing the install line. Published in README (owner/repo form, per the docs) on 2026-07-20 in 5bed4b6, alongside the 1.7.1 docs — measured from git log, not from this file's own claim. No shelf page exists to record as liveUrl, so ADR 0002's accepted arm is structurally unreachable here; a README anchor would be self-endorsement, the 2026-08-23 cursor-plugin defect. Available to users since 2026-08-27 on ADR 0007's third arm: the install is observed end to end by the named probe on claude 2.1.195 (marketplace add → appears in list → install → plugin list reports enabled), each step judged on output because `claude plugin` exits 0 on failure.

Support Status

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

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

Official Sources

• https://code.claude.com/
• https://github.com/anthropics/claude-code