Developer · Remote MCP server
Writing Style Checker
Prose linter + AI-slop detector: weasel words, passive voice, hedging, and research-cited AI tells.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.theserverlessdev/wsc- Version
- 2.2.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-14
- Updated
- 2026-07-14
- Publisher
- theserverlessdev (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/theserverlessdev) · how
- Repository
- github.com/theserverlessdev/wsc
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://wsc.theserverless.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- writing-style-checker 2.2.2 · protocol 2025-03-26
- Tools discovered
- 3:
check_text,fix_duplicates,list_word_lists - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | wsc-mcp | 2.2.2 | stdio |
How to connect Writing Style Checker
Writing Style Checker is a remote MCP server: there is nothing to install. Its endpoint is https://wsc.theserverless.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: wsc-mcp version 2.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y wsc-mcp@2.2.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"wsc": {
"command": "npx",
"args": [
"-y",
"wsc-mcp@2.2.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| WpfPilot MCPAutomate Windows WPF apps from AI agents with semantic UIA selectors and FlaUI test generation. | Local · stdio |
| WrapsSearch the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication. | Remote · HTTPLive check: ✓ handshake |
| writCommit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log. | Local · stdio |
| WriteflowGet today's WriteFlow daily writing prompt and weekly £10 writing contest info (writeflow.ink). | Remote · HTTPLive check: ✓ handshake |
| Wsjtx MCPOperate WSJT-X (FT8/FT4/WSPR) from MCP clients over its UDP message protocol. | Local · stdio |
| wydLocal runtime provenance for coding agents. Inspect sessions and explain which one owns a process. | Local · stdio |
| X402 GitBuy private git repos and agent skills with USDC over x402. Read the manifest free, then pay. | Remote · HTTPLive check: ✗ no handshake |
| x402 Micro TollgateX402 HTTP 402 + MCP paywall: charge USDC per agent call. Self-host via npx or Docker. | Local · stdio |