ctxlint (Yaw Labs)
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @yawlabs/ctxlint 0.28.2 (MIT; repo YawLabs/ctxlint). Installed pinned with scripts off (npm --ignore-scripts) and launched with `serve`: initialize and tools/list over stdio succeeded with no credentials and listed 7 tools (7 annotated by the server: 6 read-only, 1 destructive). Real calls: 3 of 3 real function calls passed.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): pass. 3 of 3 real function calls passed. Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 1156 tokens, cl100k estimate (7 tools, measured 2026-11-13 UTC, version 0.28.2). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 0 read, 0 write (state-changing), 7 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
ctxlint_audit— unclassifiedctxlint_fix— unclassifiedctxlint_mcp_audit— unclassifiedctxlint_session_audit— unclassifiedctxlint_skill_audit— unclassifiedctxlint_token_report— unclassifiedctxlint_validate_path— unclassified
handshake and tools listed without a recorded key or OAuth
Score 100/100 · Tools 7 · Token cost approx. 1,156 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.28.2 · Package @yawlabs/ctxlint · Repo YawLabs/ctxlint
Summary: ctxlint (Yaw Labs) completed an MCP handshake without credentials and exposed 7 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 7
- Context cost
- approx. 1156 tokens, cl100k estimate (7 tools, measured 2026-11-13 UTC, version 0.28.2; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @yawlabs/ctxlint (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 7 tools listed in 2.5s. |
| maintenance | pass | 25 | Repo pushed 1 days before test; 12 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 1156 tokens, cl100k estimate for 7 tools · about 14% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 7 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
c7fe64923053: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@yawlabs/ctxlint",
"version": "0.28.2",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 7,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @yawlabs/ctxlint` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 7 tools listed in 2.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 1 days before test; 12 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y @yawlabs/ctxlint serve
Pin the version we tested
npx -y @yawlabs/ctxlint@0.28.2 serve
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"ctxlint-yaw-labs": {
"command": "npx",
"args": [
"-y",
"@yawlabs/ctxlint@0.28.2",
"serve"
]
}
}
}Tools listed
ctxlint_audit, ctxlint_validate_path, ctxlint_token_report, ctxlint_fix, ctxlint_mcp_audit, ctxlint_session_audit, ctxlint_skill_audit
Quick config
{
"mcpServers": {
"ctxlint-yaw-labs": {
"command": "npx",
"args": [
"-y",
"@yawlabs/ctxlint",
"serve"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @yawlabs/ctxlint(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (7 in our test).
{
"mcpServers": {
"ctxlint-yaw-labs": {
"command": "npx",
"args": [
"-y",
"@yawlabs/ctxlint",
"serve"
]
}
}
}Test history
- 2026-11-13 UTC: New
Related: Best dev MCP servers
FAQ
Is ctxlint (Yaw Labs) deprecated?
No. @yawlabs/ctxlint was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces ctxlint (Yaw Labs)?
Nothing; ctxlint (Yaw Labs) is not deprecated as of 2026-11-13 UTC.
Does ctxlint (Yaw Labs) need an API key?
No. It completed an MCP handshake with no credentials and listed 7 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.