Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.calllint/calllint

NPM · CALLLINT-MCP · SCANNED SEP 20

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

Available components

npm · calllint-mcp 92
0 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to calllint/calllint). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 68 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 481 tokens (~80/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.calllint/calllint MCP server?

io.github.calllint/calllint runs locally as an npm package, launched with npx -y calllint-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · calllint-mcp

# add to Claude Code
claude mcp add calllint-calllint -- npx -y calllint-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "calllint-calllint": {
      "command": "npx",
      "args": [
        "-y",
        "calllint-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "calllint-calllint": {
      "command": "npx",
      "args": [
        "-y",
        "calllint-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add calllint-calllint -- npx -y calllint-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "calllint-calllint": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "calllint-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add calllint-calllint --command npx --arg -y --arg calllint-mcp
# ~/.hermes/config.yaml
mcp_servers:
  calllint-calllint:
    command: "npx"
    args: ["-y", "calllint-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "calllint-calllint": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "calllint-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add calllint-calllint -t stdio -c npx -a -y calllint-mcp
// mcp.json
{
  "mcpServers": {
    "calllint-calllint": {
      "command": "npx",
      "args": [
        "-y",
        "calllint-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/calllint-mcp@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo calllint/calllint
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/calllint/calllint/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.2.0
Rekor log index 2158640533
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:2954ca856a32ff544d2728b03d4d0919e6df925f403cab572f62a3f3ce9df4d41a1195e96a698ae0e70a500a9141ffe8f7306e9e3136be59cbcb5ce90

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~436 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_finding ~66

Return the full evidence-backed explanation for the servers in an MCP config JSON (why each verdict was reached).

NameTypeReqDescription
jsonstringyesMCP config JSON.
serverstring–Optional server name to explain (default: all).
surfacestring–Optional surface label.

No output schema declared.

No examples provided.

generate_agent_rule ~79

Generate the CallLint agent-safety rule text for a host (e.g. claude, cursor, copilot, agents). Paste into the host's rules file.

NameTypeReqDescription
hoststringyesTarget host. One of: claude, agents, cursor, copilot, codex, gemini, windsurf, cline, command.

No output schema declared.

No examples provided.

generate_ci_gate_snippet ~76

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=scan-all is report-only.

NameTypeReqDescription
modestring–CI gate mode. One of: drift, scan-all. Default: drift.

No output schema declared.

No examples provided.

scan_mcp_config_json ~70

Scan MCP config JSON text and return compact decisions (one per server: verdict, fingerprint hash, reason codes). Static; never executes the server.

NameTypeReqDescription
jsonstringyesRaw MCP config JSON.
surfacestring–Optional surface label (e.g. .cursor/mcp.json).

No output schema declared.

No examples provided.

scan_mcp_config_path ~50

Scan an MCP config file on disk and return the full ScanReport (verdict + evidence). Static; never executes the server.

NameTypeReqDescription
pathstringyesPath to the MCP config file.

No output schema declared.

No examples provided.

verify_baseline ~95

Compare a fresh scan of MCP config JSON against a recorded baseline and report drift / rug-pull signals. Static; never executes the server.

NameTypeReqDescription
baselinestring–Optional baseline JSON (calllint.baseline.v0). If omitted, a baseline is built from `json` and returned for first-time approval.
jsonstringyesCurrent MCP config JSON to verify.
surfacestring–Optional surface label.

No output schema declared.

No examples provided.

Common questions

What is the io.github.calllint/calllint MCP server?

io.github.calllint/calllint is an MCP server listed in the public MCP registry as io.github.calllint/calllint. Static preflight safety gate for MCP servers, scan configs before you run them. Never executes. This page covers its npm package (calllint-mcp).

Is the io.github.calllint/calllint MCP server safe to use?

io.github.calllint/calllint scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.calllint/calllint MCP server expose?

io.github.calllint/calllint exposes 6 tools: scan_mcp_config_path, scan_mcp_config_json, verify_baseline, explain_finding, generate_agent_rule, generate_ci_gate_snippet. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.

Is the io.github.calllint/calllint MCP server still maintained?

io.github.calllint/calllint is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.calllint/calllint MCP server under?

io.github.calllint/calllint declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.