WSC - Writing Style Checker

MCP开发工具

提供方 theserverlessdev

开发工具 HTTP · 远程 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

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 服务器,HTTP · 远程,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权会话登录 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

linter technical writing ai detection mcp mcp server github action documentation

支持客户端

适用场景

lintertechnical writingai detection

安装与配置

HTTP · 远程 会话登录
连远程 HTTPS 端点,通常为 Streamable HTTP
https://wsc.theserverless.dev/mcp

把它填进客户端的 MCP 配置即可,不需要在本地安装运行时。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
WSC - Writing Style Checker当前 未标注 HTTP · 远程 远程部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方theserverlessdev上游标注的维护方 theserverlessdev
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.5 KB
来自项目仓库与上游目录的原文,未做删改

Writing Style Checker

A prose linter and AI-slop detector. WSC finds AI tells — words, phrases, and sentence structures overrepresented in AI-generated text, each flag backed by a published corpus study. It also catches classic writing issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, and filler adverbs. Available as a web editor, HTTP API, MCP server, CLI, and GitHub Action.

Live: wsc.theserverless.dev

Features

  • 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
  • GitHub Action - Run checks in CI with ::warning annotations
  • Configurable - Customize detectors with .wscrc.json files

What WSC is (and isn't)

WSC flags patterns that research on AI-generated text finds overrepresented, and cites a source for every flag. It does not, and cannot, prove authorship. Classifier-based detectors carry a documented false-accusation risk: a Stanford study found that seven of them misflagged 61% of essays written by non-native English speakers. WSC avoids that trap by design — every flag is a specific, explainable edit that improves the text no matter who, or what, wrote it.


Detection Rules

Detector Items Description
Weasel Words 95 words/phrases Vague terms like "very", "basically", "arguably", "numerous"
Passive Voice 260 irregular verbs Auxiliary verbs + past participles (regular -ed + irregular)
Duplicate Words — Adjacent repeated words across whitespace, case-insensitive
Long Sentences threshold: 30 words Sentences exceeding a configurable word count
Nominalizations 245 word pairs Nouns replaceable with verbs ("utilization" → "use")
Hedging 100 phrases Phrases that weaken assertions ("I think", "it seems")
Filler Adverbs 139 words Adverbs adding emphasis without substance ("totally", "utterly")
AI Tells 98 words (+111 inflected forms) + 83 phrases + 12 structural patterns Words, phrases, and sentence constructions overrepresented in AI-generated text (delve, rich tapestry, It's not just X — it's Y)

Word lists sourced from Matt Might's shell scripts and expanded with additional entries. AI tells draw on published corpus studies: Kobak et al. 2025 (Science Advances), Juzek & Ward 2025 (COLING), Liang et al. 2024 (Stanford), and Reinhart et al. 2025 (PNAS). Wikipedia's editor-maintained Signs of AI writing catalogue and AI-detection vendor reports round out the sources.


Configuration

Create a .wscrc.json to customize detectors. All tools (API, MCP, CLI) support it.```json
{
"$schema": "https://wsc.theserverless.dev/schema.json",
"ignore": ["CHANGELOG.md", "docs/vendor/**"],
"detectors": {
"weaselWords": {
"enabled": true,
"add": ["synergy", "leverage"],
"remove": ["very"]
},
"longSentences": { "maxWords": 25 },
"adverbs": { "enabled": false }
}
}


Every field is optional. Missing fields use defaults. JSON Schema provides autocompletion in VS Code.

`ignore` is an array of glob patterns relative to the working directory. The GitHub Action uses the repository root. The CLI adds these patterns to its built-in `**/node_modules/**` and `**/.git/**` skips, together with the Action `exclude` input and the CLI `--ignore` flag.

---

## API Usage

### `POST /api/check`

Analyze text for writing style issues. Accepts optional `config` object.```bash
curl -X POST https://wsc.theserverless.dev/api/check \
  -H "Content-Type: application/json" \
  -d '{"text":"The code was written very quickly."}'

Response:```json
{
"summary": {
"total": 2,
"weaselWords": 1,
"passiveVoice": 1,
"duplicateWords": 0,
"longSentences": 0,
"nominalizations": 0,
"hedging": 0,
"adverbs": 0
},
"issues": {
"weaselWords": [{ "word": "very", "index": 21, "line": 1, "column": 22, "context": "..." }],
"passiveVoice": [{ "phrase": "was written", "index": 9, "line": 1, "column": 10, "context": "..." }],
"duplicateWords": [],
"longSentences": [],
"nominalizations": [],
"hedging": [],
"adverbs": []
},
"meta": { "characterCount": 34, "wordCount": 6, "sentenceCount": 1, "processingTimeMs": 2 }
}


**With config:**```bash
curl -X POST https://wsc.theserverless.dev/api/check \
  -H "Content-Type: application/json" \
  -d '{"text":"The code was written very quickly.", "config":{"detectors":{"weaselWords":{"enabled":false}}}}'

GET /api/check

Returns API documentation as JSON.

GET /api/detectors

Returns the list of all 8 detectors with descriptions, configurability, and word counts.

GET /health

Runs a smoke test with known text and returns {"status":"healthy"} or 503.

Limits: Max 100,000 characters per request. CORS enabled for all origins.


MCP Server

The Writing Style Checker is available as an MCP server, letting AI assistants check your writing directly.

Tools

Tool Description
check_text Analyze text for all 8 writing style issues. Accepts optional config.
fix_duplicates Remove duplicate adjacent words and return cleaned text
list_word_lists Return info about all detector word lists
check_file (Local only) Read a file from disk and analyze it. Auto-discovers .wscrc.json.

Remote MCP Server

Connect any MCP client to the hosted server - no installation required.```json
{
"mcpServers": {
"writing-style-checker": {
"type": "url",
"url": "https://wsc.theserverless.dev/mcp"
}
}
}


### Local MCP Server (stdio)

Install via npm for local usage. Includes `check_file` for analyzing files on disk with auto-discovery of `.wscrc.json`.```bash
npx wsc-mcp

Claude Desktop / Claude Code config:```json
{
"mcpServers": {
"writing-style-checker": {
"command": "npx",
"args": ["wsc-mcp"]
}
}
}


See the `wsc-mcp` npm page for full documentation.

---

## CLI

Check files from the command line.```bash
# Check all markdown files
npx wsc-lint check "**/*.md"

# Read from stdin
echo "The code was written very quickly." | npx wsc-lint check --stdin

# JSON output for scripting
npx wsc-lint check "**/*.md" --format json

# GitHub Actions annotations
npx wsc-lint check "**/*.md" --format github

# Create a config file
npx wsc-lint init

See the wsc-lint README for full documentation.


GitHub Action```yaml

  • uses: theserverlessdev/wsc@v1
    with:
    files: '/*.md'
    max-warnings: 20
    exclude: |
    CHANGELOG.md
    vendor/

| Input | Default | Description |
|-------|---------|-------------|
| `files` | `**/*.md` | Glob pattern for files to check |
| `config` | — | Path to `.wscrc.json` config file |
| `max-warnings` | unlimited | Max warnings before failing |
| `only-changed` | `false` | On a pull request, check changed files that match `files`. If none match, skip the check. Other events check `files`. |
| `exclude` | — | Glob patterns to skip. Separate with a comma or a new line. Adds to config `ignore`. |

---

## Privacy

The web editor runs **in your browser** - we never send text to any server. The API and MCP endpoints only process text you explicitly send to them.

---

## Project Structure```
.
├── src/
│   ├── core/                    # Shared detection engine
│   │   ├── detector.ts          # 8 detection algorithms
│   │   ├── words.ts             # Word/phrase lists (800+ entries)
│   │   ├── config.ts            # Config types, merging, validation
│   │   ├── config-node.ts       # Node-only: file loading, discovery
│   │   ├── analyzer.ts          # Unified analyzeText() entry point
│   │   └── index.ts             # Public API exports
│   ├── docs/                    # Documentation content (Markdown files)
│   ├── mcp/
│   │   └── handler.ts           # MCP JSON-RPC 2.0 handler
│   ├── lib/
│   │   ├── App.svelte           # Main editor page component
│   │   ├── stores/theme.ts      # Theme store (light/dark/system)
│   │   └── components/          # UI components (StatsBar, ConfigPanel, etc.)
│   ├── routes/
│   │   ├── +layout.svelte       # Shared layout (header, nav, footer)
│   │   ├── api/check/+server.ts # HTTP API endpoint
│   │   ├── mcp/+server.ts       # MCP endpoint
│   │   ├── health/+server.ts    # Health check endpoint
│   │   ├── docs/+page.svelte    # Documentation page
│   │   └── words/+page.svelte   # Word library browser
│   └── styles/
│       └── main.scss            # Global styles (light + dark themes)
├── mcp-server/                  # Standalone stdio MCP server (npm: wsc-mcp)
├── cli/                         # CLI tool (npm: wsc-lint)
├── action/                      # GitHub Action (composite)
├── tests/                       # 341 tests across 18 files
├── static/
│   ├── schema.json              # JSON Schema for .wscrc.json
│   ├── llms.txt                 # AI/LLM discovery file
│   └── llms-full.txt            # Detailed LLM context
├── wrangler.toml                # Cloudflare Workers config
└── svelte.config.js             # SvelteKit configuration

Local Development```bash

git clone https://github.com/theserverlessdev/wsc.git
cd wsc
npm install
npm run dev


Visit `http://localhost:5173`. The API is at `/api/check`, MCP at `/mcp`, health at `/health`.

### Commands

| Command | Description |
|---------|-------------|
| `npm run dev` | Start dev server |
| `npm run build` | Build for production |
| `npm run check` | Type check with svelte-check |
| `npm test` | Run all 341 tests |
| `npm run test:coverage` | Coverage report |

## Deployment

Deployed as a Cloudflare Worker at `wsc.theserverless.dev`.```bash
npm run build
npx wrangler deploy

Contributing

See CONTRIBUTING.md for development setup, testing, and pull request guidelines.

For substantial changes, please open an issue first.

Acknowledgements

  • Matt Might for the original shell scripts
  • Built with SvelteKit and Svelte 5, deployed on Cloudflare Workers
  • Logo made with DiffusionBee

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
WSC - Writing Style Checker 怎么安装?

在客户端按下面的安装命令接入:https://wsc.theserverless.dev/mcp。装完在客户端配置里引用同一个包或端点。

WSC - Writing Style Checker 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

WSC - Writing Style Checker 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

WSC - Writing Style Checker 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

WSC - Writing Style Checker 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

WSC - Writing Style Checker 能提供哪些能力?

资料显示能力标签包括 linter、technical writing、ai detection、mcp、mcp server、github action。具体工具清单以官方文档为准。

WSC - Writing Style Checker 需要什么运行环境?

运行时为 node;属于远程端点,不需要在本地装运行时。

WSC - Writing Style Checker 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。