# calllint-mcp

Static preflight safety gate for MCP servers — scan configs before you run them. Never executes.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (publisher, @saintl1022)
- **Version:** 0.2.0
- **Author:** io.github.calllint
- **License:** Unknown
- **npm:** calllint-mcp
- **Source:** https://github.com/calllint/calllint
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: yes
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-28T18:10:16.158Z
- **Version scanned:** 0.2.0
- **CVEs:** none found by OSV at scan time
**Findings**
- shipped source (note) in `dist/index.js`: Very large base64-looking blob in source

## Tools

6 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scan_mcp_config_path` — Scan an MCP config file on disk and return the full ScanReport (verdict + evidence). Static; never executes the server.
- `scan_mcp_config_json` — Scan MCP config JSON text and return compact decisions (one per server: verdict, fingerprint hash, reason codes). Static; never executes the server.
- `verify_baseline` — Compare a fresh scan of MCP config JSON against a recorded baseline and report drift / rug-pull signals. Static; never executes the server.
- `explain_finding` — Return the full evidence-backed explanation for the servers in an MCP config JSON (why each verdict was reached).
- `generate_agent_rule` — Generate the CallLint agent-safety rule text for a host (e.g. claude, cursor, copilot, agents). Paste into the host's rules file.
- `generate_ci_gate_snippet` — Generate a GitHub Actions workflow (.github/workflows/calllint.yml) that gates a repo on its agent-tool surface. mode=drift fails on approved-state drift; mode=

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"calllint\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"calllint-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 11, ceiling 29 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/calllint-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/calllint-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/calllint-mcp
- HTML page: https://forgeregistry.com/registry/calllint-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.