Writing Style Checker
REMOTE · WSC.THESERVERLESS.DEV · 2 COMPONENTS · SCANNED SEP 22
Prose linter + AI-slop detector: weasel words, passive voice, hedging, and research-cited AI tells
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 409 tokens (~136/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "fix_duplicates" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the Writing Style Checker MCP server?
Writing Style Checker is a hosted endpoint at https://wsc.theserverless.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wsc.theserverless.dev
claude mcp add --transport http theserverlessdev-wsc 'https://wsc.theserverless.dev/mcp'
{
"mcpServers": {
"theserverlessdev-wsc": {
"url": "https://wsc.theserverless.dev/mcp"
}
}
} {
"servers": {
"theserverlessdev-wsc": {
"type": "http",
"url": "https://wsc.theserverless.dev/mcp"
}
}
} [mcp_servers.theserverlessdev-wsc] url = "https://wsc.theserverless.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theserverlessdev-wsc": {
"type": "remote",
"url": "https://wsc.theserverless.dev/mcp",
"enabled": true
}
}
} openclaw mcp add theserverlessdev-wsc --url 'https://wsc.theserverless.dev/mcp' --transport streamable-http
mcp_servers:
theserverlessdev-wsc:
url: "https://wsc.theserverless.dev/mcp" {
"McpServers": {
"theserverlessdev-wsc": {
"Transport": "http",
"Url": "https://wsc.theserverless.dev/mcp"
}
}
} assistant mcp add theserverlessdev-wsc -t streamable-http -u 'https://wsc.theserverless.dev/mcp'
{
"mcpServers": {
"theserverlessdev-wsc": {
"type": "http",
"url": "https://wsc.theserverless.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://wsc.theserverless.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=theserverless.dev | CN=WE1,O=Google Trust Services,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | dbf52e8aad3ede4a13ac2868e90a773e |
| SANs: theserverless.dev, wsc.theserverless.dev, *.wsc.theserverless.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wsc.theserverless.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| theserverless.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wsc.theserverless.dev/mcp | Verified | 200 | |
| http (plaintext) | http://wsc.theserverless.dev/mcp | HTTPS enforced | 301 | https://wsc.theserverless.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_text Check text for writing style issues ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Optional config to enable/disable detectors or add/remove word-list entries; same schema as .wscrc.json (https://wsc.theserverless.dev/schema.json) |
| format | string | – | Set to "markdown" to mask code blocks, inline code, tables, and headings so they are not linted as prose; default "plain" lints everything |
| text | string | yes | The text to analyze for writing style issues |
No output schema declared.
No examples provided.
fix_duplicates Remove duplicate adjacent words ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to clean by removing duplicate adjacent words |
No output schema declared.
No examples provided.
list_word_lists List detector word lists ~77
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Writing Style Checker MCP server?
Writing Style Checker is an MCP server listed in the public MCP registry as io.github.theserverlessdev/wsc. Prose linter + AI-slop detector: weasel words, passive voice, hedging, and research-cited AI tells. This page covers its hosted endpoint (https://wsc.theserverless.dev/mcp).
Is the Writing Style Checker MCP server safe to use?
Writing Style Checker scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Writing Style Checker MCP server expose?
Writing Style Checker exposes 3 tools: check_text, fix_duplicates, list_word_lists. Their descriptions and schemas cost roughly 409 tokens of context every time the server is loaded.
Does the Writing Style Checker MCP server require authentication?
No. We connected to Writing Style Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Writing Style Checker MCP server still maintained?
Writing Style Checker is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.