WSC - Writing Style Checker
Related Servers
Alternatives to WSC - Writing Style Checker
- AlicenseAqualityFmaintenanceIntegrates Vale prose linting into AI coding assistants, enabling users to check text files for style and grammar issues using Vale's powerful linting engine. Provides automated style feedback with smart configuration discovery and rich formatted results.318MIT
- AlicenseAqualityCmaintenanceProvides automated grammar checking by intercepting user input and returning correction instructions for MCP-compatible clients like Claude Desktop and Claude Code.14 npmMIT
- AlicenseAqualityCmaintenanceDeterministic fluff detector for AI-generated prose. No model, no API key.31MIT
Related Servers
- AlicenseAqualityBmaintenanceA private, open-source AI-text checker. Get a read on whether text looks AI-written, the exact AI-tell spans to fix, a reuse check, and a grammar pass.4MIT
- AlicenseAqualityCmaintenanceEnables detection and elimination of AI slop in text, providing tools to analyze writing for overused phrases, structural issues, and verbosity, and offers human writing rules tailored to context.32MIT
- AlicenseAqualityAmaintenanceBilingual (EN/ES) AI-writing detection that shows the evidence instead of a percentage: named tells with line and column, hidden-character inspection, and citation cross-checking against a document's own bibliography. Seven of its nine tools run entirely locally and never touch the network.1023MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI content detection with sentence-level and paragraph-level AI probability scoring to identify and fix AI-generated text.MIT
- FlicenseAqualityBmaintenanceL1-aware grammar, style, translation & tone tools with 70 local rules. Zero API keys needed.4-
- AlicenseNot gradedqualityAmaintenanceZero Slop edits AI-assisted writing through MCP, reducing stock phrasing and repetition while checking grammar and flow. It returns the rewrite with writing scores and flags detected changes to names, numbers, quotations, and links.1,629 npm117MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: check_file vs check_text differ by input source, fix_duplicates is for fixing a specific issue, and list_word_lists provides reference data. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (check_file, check_text, fix_duplicates, list_word_lists), making the API predictable.
With 4 tools, the server is well-scoped for a writing style checker: two input methods for analysis, one fix action, and one list action. Not overly sparse or heavy.
The tool surface covers core checking and duplicate removal, but lacks auto-fix for other issue types (e.g., weasel words, passive voice). Users must manually edit text after reports, which is a minor gap.