PJQ — Public Judgment Quotient

life.pjqPublished by pjq.lifeOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

PJQ analyzes YouTube comments and returns a reception verdict — a mood score plus a stance breakdown — so an assistant can gauge how an audience received a…

What you can do
  • Run an analysis on a piece of content by its URL, sampling the comments beneath it.
  • Read verdicts: a numeric mood score plus counts of substantive support, pushback and neutral opinion.
  • See how much of the discussion is noise — off-topic, thin praise, bots or self-promoters — reported separately from opinion metrics.
  • Read-only lookups are described as free of credits; a full analysis consumes one credit.
When to use it
Useful when you want an assistant to judge audience reception of a video or other media rather than just its view counts, for example to compare how different audiences reacted or to separate genuine opinion from bot and promotional noise.
Requirements
Remote MCP endpoint at pjq.life over streamable HTTP. A bearer API key is required in the Authorization header; a free key is created in the Cabinet on the site. Network access to the hosted service is needed; the analysis engine itself is closed and hosted.
Before you install
The Authorization header carries a secret API key — keep it out of logs and shared transcripts. Full analyses consume credits, so repeated runs can use up an allowance. Analyses are sent to a third-party hosted service, and comment data is processed there; only aggregates and a few exemplars come back, not raw comment texts.

Installation

In SourceWeft

  1. Open PJQ — Public Judgment Quotient in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/life.pjq%2Fpjq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

Source: README.md at commit cf65787

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts