ctxlint
NPM · @YAWLABS/CTXLINT
Lint AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase
Available components
Last scanned (1 hour ago)
Scores higher than 39% of npm servers
Category Developer Tools
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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 935 tokens (~133/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 +15
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 0.28.0 → 0.28.1 functional
- 15 Oct 26 0
- Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −1
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: pass → unverified ▼ functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.27.3 → 0.28.0 functional
- 29 Sept 26 0
- Package version: 0.27.2 → 0.27.3 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Analysed npm/@yawlabs/ctxlint@0.28.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ctxlint_audit ~107
Audit AI agent context files (CLAUDE.md, AGENTS.md, etc.) in the project. Checks for stale references, invalid commands, redundant content, contradictions, frontmatter issues, and token waste. Scoped to context-file checks only; MCP-config and session-level checks are exposed as separate tools.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Which context-file checks to run. Defaults to all. |
| projectPath | string | – | Path to the project root. Defaults to current working directory. |
No output schema declared.
No examples provided.
ctxlint_fix ~122
Run the linter with --fix mode to auto-correct broken file paths in context files using git history and fuzzy matching. Returns a summary of what was fixed. Pass dryRun: true to preview what would be fixed without writing any files.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Which context-file checks to run before fixing. Defaults to all. |
| dryRun | boolean | – | If true, simulate fixes and report what would change without writing any files. Returns accurate counts. |
| projectPath | string | – | Path to the project root. Defaults to current working directory. |
No output schema declared.
No examples provided.
ctxlint_mcp_audit ~102
Lint MCP server configuration files in a project. Checks for schema errors, hardcoded secrets, deprecated transports, wrong env var syntax, URL issues, and cross-client inconsistencies.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Specific MCP checks to run (default: all mcp-* checks). |
| includeGlobal | boolean | – | Also scan global/user-level MCP configs. |
| projectPath | string | – | Path to the project root. Defaults to current working directory. |
No output schema declared.
No examples provided.
ctxlint_session_audit ~139
Audit AI agent session data for cross-project consistency and session hazards. Checks for missing GitHub secrets, diverged config files and missing workflows across sibling repositories; stale, duplicate or overflowing memory entries; command loops; and, from Claude Code transcripts, shared temp paths, gates claimed clean after failing, edits piling up on the default branch, unresolvable commit SHAs in memory, and large whole-file Reads re-sent as context on later turns.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Specific session checks to run (default: all session-* checks). |
| projectPath | string | – | Path to the project root. Defaults to current working directory. |
No output schema declared.
No examples provided.
ctxlint_skill_audit ~99
Audit agent skill and subagent definitions (~/.claude/skills/*/SKILL.md, ~/.claude/agents/*.md). Checks for frontmatter problems, broken file references, trigger collisions, orphaned skill directories, and dead tool restrictions.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Specific skill checks to run (default: all skill-* checks). |
| projectPath | string | – | Path to the project root. Defaults to current working directory. |
No output schema declared.
No examples provided.
ctxlint_token_report ~52
Get a token count breakdown for all context files in the project. Shows per-file and aggregate token usage, plus estimated waste from redundant content.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Project root. Defaults to cwd. |
No output schema declared.
No examples provided.
ctxlint_validate_path ~65
Check if a file path referenced in a context file actually exists in the project. Returns the file status and suggests corrections if the path is invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The file path to validate |
| projectPath | string | – | Project root. Defaults to cwd. |
No output schema declared.
No examples provided.
How do I install the ctxlint MCP server?
ctxlint runs locally as an npm package, launched with npx -y @yawlabs/ctxlint. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @yawlabs/ctxlint
claude mcp add yawlabs-ctxlint -- npx -y @yawlabs/ctxlint
What is the ctxlint MCP server?
ctxlint is an MCP server listed in the public MCP registry as io.github.YawLabs/ctxlint. Lint AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase. This page covers its npm package (@yawlabs/ctxlint).
Is the ctxlint MCP server safe to use?
ctxlint scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 ctxlint MCP server expose?
ctxlint exposes 7 tools: ctxlint_audit, ctxlint_validate_path, ctxlint_token_report, ctxlint_fix, ctxlint_mcp_audit, and 2 more. Their descriptions and schemas cost roughly 686 tokens of context every time the server is loaded.
Is the ctxlint MCP server still maintained?
ctxlint is still listed as active in the MCP registry. We last reached this channel on 5 November 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 ctxlint MCP server under?
ctxlint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.