MCP.so
Sign In
Q

QED MCP Server

@onebit0fme

Basic information

Category

Other

Transports

stdio

Auth

oauth

Author

onebit0fme

Submitted by

Taras Yanchynskyy

About QED MCP Server

Scores your writing against quality profiles — per-trait breakdown, deterministic, sub-second. No auth required.

QED MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "qed": {
      "type": "http",
      "url": "https://qed.systems/mcp"
    }
  }
}

QED MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is QED?

QED is a deterministic scoring tool that evaluates text against quality profiles built from example documents. It returns a composite score and a per-trait breakdown, identifying weak areas and their magnitude. Designed for developers and technical writers, it works with profiles for READMEs, landing pages, technical writing, and more.

How to use QED?

Add QED to Claude Code via claude mcp add --transport http qed https://qed.systems/mcp. Then use the commands /qed:score, /qed:improve, or /qed:profile directly in Claude Code. No signup or authentication is required.

Key features of QED

  • Deterministic scoring – same content, same profile, same result every time.
  • Multiple quality profiles for different document types.
  • Per-trait breakdown showing exact weaknesses.
  • No LLM at inference – scores work in CI, scripts, or interactively.
  • No auth, no signup required.

Use cases of QED

  • Scoring a README against the qed.compelling-readme profile.
  • Evaluating landing page copy with qed.developer-landing-page.
  • Checking technical documentation against qed.technical-writing.
  • Testing content quality in CI pipelines without nondeterminism.

Frequently asked questions

1

How does QED differ from using an LLM to score content?

QED is fully deterministic – same content and profile always produce the same score, with no LLM at inference time. This makes it suitable for CI scripts, automated checks, and reproducible evaluations.

2

What runtime or dependencies does QED require?

No runtime or dependencies beyond the MCP client (e.g., Claude Code). QED runs as a remote service – simply add it via `claude mcp add`.

3

Where does my data go?

QED processes text over HTTP. The README does not specify data retention or storage policies beyond stating no signup or auth.

4

What profiles are available?

Four profiles are mentioned: `qed.compelling-readme`, `qed.technical-writing`, `qed.developer-landing-page`, and `qed.puns`.

5

Is authentication or registration needed?

No. QED does not require any authentication or signup to use.

Comments

More Other MCP servers