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.raunakkathuria/lexilint

NPM · LEXILINT-MCP

Offline spell checker + BYOK grammar for AI assistants. Works with Claude Desktop, ChatGPT, Cursor.

Available components

0 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 53% of npm servers

Category Developer Tools

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 52 of 143 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency32
  • 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
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 31 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 443 tokens (~147/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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.

  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −6
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 16 Oct 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.

  • 14 Oct 26 −3
    • Stability: pass → 0.80 functional
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 4 Nov 2026 · Analysed npm/lexilint-mcp@1.2.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 143 packages
Packages resolved 143
Deprecated 1
Stale 51
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~443 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
check_text ~184

Run spell check and optionally grammar check. Spell check (en-US/en-GB) is free and offline. Grammar with Gemini is free (BYOK). Multi-language and OpenAI/Anthropic require LexiLint Premium.

NameTypeReqDescription
api_keystring–Optional per-call API key override; otherwise uses the selected provider environment variable
languagestring–Language code. Free: en-US, en-GB. Premium: fr, de, es, ru, pl, tr.
license_keystring–LexiLint Premium license key (for premium languages or providers)
modelstring–Optional provider model ID. Custom models require LexiLint Premium.
providerstring–AI provider. "gemini" is free. "openai"/"anthropic" require Premium.
textstringyesThe text to check

No output schema declared.

No examples provided.

grammar_check ~193

Check text for grammar, style, and clarity issues. Free with Google Gemini (BYOK — get a free key at aistudio.google.com). OpenAI and Anthropic require LexiLint Premium.

NameTypeReqDescription
api_keystring–Optional per-call API key override; otherwise uses the selected provider environment variable
languagestring–Language code (en-US, en-GB free; fr, de, es, ru, pl, tr require Premium)
license_keystring–LexiLint Premium license key (required for openai/anthropic providers)
modelstring–Optional provider model ID. Custom models require LexiLint Premium.
providerstringyes"gemini" is free (get key at aistudio.google.com). "openai" and "anthropic" require LexiLint Premium.
textstringyesThe text to grammar-check

No output schema declared.

No examples provided.

spell_check ~66

Check text for spelling errors. 100% offline — no API key needed. Supports en-US and en-GB.

NameTypeReqDescription
languagestring–Language to check (en-US or en-GB, default: en-US)
textstringyesThe text to spell-check

No output schema declared.

No examples provided.

Install

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

io.github.raunakkathuria/lexilint runs locally as an npm package, launched with npx -y lexilint-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 · lexilint-mcp

# add to Claude Code
claude mcp add raunakkathuria-lexilint -- npx -y lexilint-mcp
Common questions

What is the io.github.raunakkathuria/lexilint MCP server?

io.github.raunakkathuria/lexilint is an MCP server listed in the public MCP registry as io.github.raunakkathuria/lexilint. Offline spell checker + BYOK grammar for AI assistants. Works with Claude Desktop, ChatGPT, Cursor. This page covers its npm package (lexilint-mcp).

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

io.github.raunakkathuria/lexilint scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 io.github.raunakkathuria/lexilint MCP server expose?

io.github.raunakkathuria/lexilint exposes 3 tools: spell_check, grammar_check, check_text. Their descriptions and schemas cost roughly 443 tokens of context every time the server is loaded.

Is the io.github.raunakkathuria/lexilint MCP server still maintained?

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