Lucidity MCP vs Wsc

In-depth architectural comparison of the Lucidity MCP and Wsc MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Lucidity MCP when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: analyze_changes, workspace_root, path.

Explore Lucidity MCP Details

Choose Wsc when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: check_text, fix_duplicates, list_word_lists.

Explore Wsc Details

Feature & Specification Comparison

Specification	Lucidity MCP hyperb1iss Monitoring	Wsc theserverlessdev Monitoring
Summary	Enhance AI-generated code quality through intelligent, prompt-based analysis across 10 critical dimensions from complexity to security vulnerabilities	Prose linter + AI-slop detector: weasel words, passive voice, hedging, and 190+ research-cited AI tells. Remote server at wsc.theserverless.dev/mcp or npx wsc-mcp.
Category & Scope	Monitoring

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "hyperb1iss-lucidity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hyperb1iss-lucidity-mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons