MCP.so
ログイン

WSC - Writing Style Checker MCP Server

@theserverlessdev

基本情報

ライセンス

MIT

作者

theserverlessdev

投稿者

Ankur Singh

WSC - Writing Style Checker MCP Server について

Prose linter + AI-slop detector: weasel words, passive voice, hedging, and 190+ research-cited AI tells. Web editor, API, MCP server, CLI, GitHub Action.

WSC - Writing Style Checker MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "wsc": {
      "command": "npx",
      "args": [
        "wsc-mcp"
      ]
    }
  }
}

WSC - Writing Style Checker MCP Server のツール

4

Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory, never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. Use this for text already in the conversation; use check_file for files on disk. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.

Remove duplicate adjacent words (case-insensitive, including across line breaks) and return the cleaned text plus the list of words that were removed. Read-only with no side effects: the fix is returned in the response, nothing is written anywhere. Use after check_text or check_file reports duplicate words; other issue types are report-only and have no auto-fix.

Return every detector word/phrase list with its entry count, config key, and sample entries, plus a link to the full browsable library. Read-only, takes no parameters, and returns the same catalog for a given release. Use it to see what the detectors match before tuning a config for check_text or check_file; not needed for ordinary checking.

Read a UTF-8 file from local disk and analyze it for the same writing style issues as check_text (weasel words, passive voice, hedging, AI tells, and more). Read-only: the file is never modified, and Markdown files are automatically masked so code blocks and tables are not linted as prose. A .wscrc.json config is auto-discovered from the file's directory upward unless config is passed explicitly. Returns the same line-and-column report as check_text, or an error message for unreadable or oversized (over 100,000 characters) files. Use when the text lives on disk; use check_text for text already in the conversation.

概要

What is Wsc?

Prose linter + AI-slop detector: weasel words, passive voice, hedging, and 190+ research-cited AI tells. Web editor, API, MCP server, CLI, GitHub Action.

How to use Wsc?

The README includes setup instructions such as npx wsc-mcp.

Key features of Wsc

  • Web Editor - Real-time highlighting with inline fix buttons for all 8 detectors
  • HTTP API - POST text with optional config, retrieve structured JSON responses
  • MCP Server (Remote) - Connect AI assistants via Streamable HTTP transport
  • MCP Server (Local) - Stdio-based server via wsc-mcp on npm
  • CLI - Check files from the command line via wsc-lint

Use cases of Wsc

  • Connect an MCP-compatible client to this repository's service.
  • Review the README-backed setup before enabling it in production.

よくある質問

1

Where is the source code for Wsc?

The source code is linked from the repository URL on this page.

2

Does Wsc include a standard MCP config?

If the README contains a parseable MCP configuration block, it is shown in the Config tab.

コメント

マーケットプレイスの他のコンテンツ