PJQ — Public Judgment Quotient

life.pjq由 pjq.life 發布官方發布者v1.0.0更新於 Oct 24, 2026

Observatory of public media reception: classify YouTube comments for mood, support and controversy.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取資料與分析

概覽

AI 產生的概覽

PJQ 分析 YouTube 留言並給出受眾接受度結論——情緒分數與立場分布——讓助理判斷某段內容被觀眾如何接收。

可以做什麼
  • 依內容連結發起分析,抽樣其下的留言。
  • 讀取結論:一個數值化的情緒分數,以及實質支持、反對與中立的數量。
  • 查看討論中有多少雜訊——離題、空泛讚美、機器人或自我推銷——這些與意見指標分開統計。
  • 據說明唯讀查詢不消耗額度,完整分析消耗一個額度。
適用情境
適合希望助理評估影片等內容的受眾反應、而不只看觀看次數時使用,例如比較不同受眾的反應,或把真實意見與機器人及推銷雜訊區分開來。
執行需求
遠端 MCP 端點,位於 pjq.life,使用 streamable HTTP。需在 Authorization 標頭提供 bearer API 金鑰,可在網站 Cabinet 免費建立。需要能連線至該託管服務的網路;分析引擎為閉源託管。
安裝前請注意
Authorization 標頭攜帶金鑰,請避免出現在日誌與共享對話中。完整分析會消耗額度,反覆執行可能用盡配額。分析請求會送往第三方託管服務並在其處處理留言資料;回傳的只有彙總資料與少量範例,不含原始留言文字。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 PJQ — Public Judgment Quotient,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/life.pjq%2Fpjq/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "pjq-public-judgment-quotient": {
      "type": "http",
      "url": "https://pjq.life/mcp/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

PJQ — Public Judgment Quotient

A seismograph for public opinion. PJQ measures how an audience actually received a piece of media — separating genuine opinion from fan noise, bots, and self-promoters.

Live: pjq.life · License: Apache-2.0


What this is

PJQ takes the URL of a piece of content (YouTube today; Reddit, Telegram, and News next), samples the comments under it, and classifies every comment against a 7-category stance rubric. The output is a verdict: a numeric reception score (mood) plus a structured breakdown — how many people substantively agreed, how many pushed back, how many stayed neutral, and how much noise is drowning the signal.

Think of it as an observatory of media reception, exposed over two transports on one core:

  • a REST API (/api/v1/*) for analytics automation, and
  • an MCP server (/mcp/) so AI agents (Claude Desktop and friends) can run analyses and read verdicts directly inside a chat.

What's in this repository

This repo is the open client + specification of PJQ. The hosted analysis engine (sampling, classification, QA, the ONNX stance model and the prompt internals) stays closed — it is the product's moat. What's open here is everything you need to use, integrate with, and understand PJQ:

web/    — the full web client (React + TypeScript + Vite SPA, 5 languages)spec/   — the conceptual specification          ├── CONCEPT.md          what PJQ is and why          ├── RUBRIC.md           the 7-category stance rubric (definitions)          ├── domains.yaml        the 11-domain content taxonomy          ├── FEATURED.md         the open, automatic showcase-ranking formula          └── verdict-schema.md   the shape of a verdict (API output)docs/   — integration reference          ├── api-reference.md    REST API surface          ├── mcp-reference.md    MCP tools and schemas          └── user-guide/         end-user guide (EN + RU)

The 7-category rubric (in one breath)

Every comment gets exactly one of: SUP (substantive support), AGA (substantive against), NEU (neutral), OFF (off-topic), THIN (thin positive — praise without an argument), SUS (inorganic — bot / paid / coordinated), AGN (own agenda — the comment is a vehicle for the author's external goal).

Reporting rule: opinion metrics (mood, support) are computed strictly from SUP / AGA / NEU. THIN / OFF / SUS / AGN are counted separately and never inflate support percentages. See spec/RUBRIC.md.

Running the web client

The client is a standard Vite SPA. By default it talks to the hosted backend at pjq.life (same-origin in production).

bash
cd webnpm installnpm run dev      # dev server with hot reloadnpm run build    # production build (with build-time SEO prerender) -> dist/

To point the client at a different backend, copy web/.env.example and set VITE_API_BASE.

Integrating

  • REST API — get an API key from the Cabinet on pjq.life, then see docs/api-reference.md. Read-only tools cost no credits; a full analysis costs one credit.
  • MCP — point an MCP-capable client at https://pjq.life/mcp/ and see docs/mcp-reference.md for the exported tools.

Comment raw texts are never returned over the API — only aggregates, percentages, and a small set of representative exemplars, per PJQ's privacy policy.

Status

PJQ is live and in active development. The roadmap is public at pjq.life/flightlog. This repository tracks the client and the spec; engine changes ship to the hosted service.

License

Copyright 2026 PJQ (github.com/Makaric). Licensed under the Apache License, Version 2.0 — see LICENSE.

Русская версия: README_RU.md.

來源:README.md,提交 cf65787

工具

0
該伺服器需要 API 金鑰等憑證,因此 SourceWeft 無法在沒有憑證的情況下讀取其工具,也未收錄。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 60%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分