MCP.so
ログイン
Q

QED MCP Server

@onebit0fme

基本情報

カテゴリ

その他

トランスポート

stdio

認証方式

oauth

作者

onebit0fme

投稿者

Taras Yanchynskyy

QED MCP Server について

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

QED MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

QED MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

このサーバーは認証が必要です。ツールの取得にはログインや提供元の認証情報が必要な場合があります。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

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.

よくある質問

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.

コメント

「その他」の他のコンテンツ