
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.
概览
PJQ 分析 YouTube 评论并给出受众接受度结论——情绪分数与立场分布——让助手判断某条内容被观众如何接收。
- 可以做什么
- 按内容链接发起分析,抽样其下的评论。
- 读取结论:一个数值化的情绪分数,以及实质性支持、反对与中立的数量。
- 查看讨论中有多少噪音——离题、空洞称赞、机器人或自我推广——这些与观点指标分开统计。
- 据说明只读查询不消耗额度,完整分析消耗一个额度。
- 适用场景
- 当希望助手评估视频等内容的受众反响、而不只看播放量时适用,例如比较不同受众的反应,或把真实观点与机器人和推广噪音区分开。
- 运行要求
- 远程 MCP 端点,位于 pjq.life,使用 streamable HTTP。需要在 Authorization 请求头中提供 bearer API 密钥,可在网站 Cabinet 中免费创建。需要能访问该托管服务的网络;分析引擎为闭源托管。
安装
在 SourceWeft 中
- 打开 控制台中的 PJQ — Public Judgment Quotient,将其添加到工作区。
- 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
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:
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).
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 seedocs/mcp-reference.mdfor 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版本历史
1- v1.0.0最新Sep 16, 2026
评分
已满足适用检查项的 60%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分