MCP.Market

Writing Style Checker MCP server

online · 100% uptime
by theserverlessdev·io.github.theserverlessdev/wsc·v2.2.2·6 stars
No reviews yet

Prose linter + AI-slop detector: weasel words, passive voice, hedging, and research-cited AI tells

B84/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
Growing

6 stars53 downloads/wk

Reviews

Write one

Nobody has reviewed Writing Style Checker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Writing Style Checker tools (3, 1 write)

write = sends, deletes, buys or posts
  • check_textFree

    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 on the hosted server and 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. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.

  • fix_duplicateswrite actionFree

    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 reports duplicate words; other issue types are report-only and have no auto-fix.

  • list_word_listsFree

    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; not needed for ordinary checking.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

1 high
  • Code scan19 source files scanned25/25
  • Live reliabilityremote reachable in 483ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenancelast push 63 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Writing Style Checker compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
97 ms
faster than 85% of 30,031 servers
GitHub stars
6
more than 85% of 28,688 servers
Downloads a week
53
more than 44% of 12,191 servers with a package

What its tools let an agent do: 2 read · 1 change

Install Writing Style Checker in Claude Code, Cursor or VS Code

claude mcp add --transport http wsc https://wsc.theserverless.dev/mcp
Add to Cursor

What the publisher says

From the Writing Style Checker repository's README, as published. We do not edit it. Read it on GitHub

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

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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Writing Style Checker: common questions

Is Writing Style Checker MCP server safe?
Mostly: it is graded B (84/100). Read the Writing Style Checker safety report
How do I install Writing Style Checker?
It runs remotely at wsc.theserverless.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Writing Style Checker need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Writing Style Checker maintained?
The last commit was 103 days ago (2026-07-24). The latest release is v2.2.2.
Is Writing Style Checker up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Writing Style Checker compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.