PJQ — Public Judgment Quotient
REMOTE · PJQ.LIFE · SCANNED AUG 3
Observatory of public media reception: classify YouTube comments for mood, support and controversy.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability49
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 662 tokens (~94/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · pjq.life
claude mcp add --transport http life-pjq-pjq https://pjq.life/mcp/
[mcp_servers.life-pjq-pjq] url = "https://pjq.life/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"life-pjq-pjq": {
"type": "remote",
"url": "https://pjq.life/mcp/",
"enabled": true
}
}
} openclaw mcp add life-pjq-pjq --url https://pjq.life/mcp/ --transport streamable-http
mcp_servers:
life-pjq-pjq:
url: "https://pjq.life/mcp/" {
"mcpServers": {
"life-pjq-pjq": {
"type": "http",
"url": "https://pjq.life/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://pjq.life/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pjq.life | CN=E8,O=Let's Encrypt,C=US | 25 May 2026 | 23 Aug 2026 | ECDSA 256 | ECDSA-SHA384 | 6fca1ba4e16583ddb952b4ce9267f2db76d |
| SANs: pjq.life | ||||||
| CN=E8,O=Let's Encrypt,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 Mar 2024 | 12 Mar 2027 | ECDSA 384 | SHA256-RSA | 63959363c24e7082715918bfc3d7ed56 |
DNSSEC insecure
Validation of pjq.life. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| life. | present | 11164 | 8 | Verified |
| pjq.life. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://i.ytimg.com https://yt3.ggpht.com https://images.unsplash.com; font-src 'self'; connect-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(), tools=(self) |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pjq.life/mcp/ | Verified | 200 | |
| http (plaintext) | http://pjq.life/mcp/ | HTTPS enforced | 301 | https://pjq.life/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
controversial_videos ~115
Самые спорные видео — высокий controversy (раскол SUP/AGA, 0..1). Для поиска тем с максимальным расколом мнений в аудитории. Отличается от mood_net (направление): controversy = размер раскола. 1.0 = война 50/50. limit: сколько вернуть (1..20, default 5). days: макс возраст вердикта (default 30).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | — | — |
| limit | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | — |
No examples provided.
mood_matrix ~112
Агрегатный mood-вью с фильтрами по домену и tier. domain ∈ {POL, ECON, BIZ, TECH, EDU, ENV, SOC, MED, TRV, ENT, LIFE, unassigned}. tier ∈ {official, semi_official, independent, unassigned}. Возвращает последние `limit` снапшотов с расчётом mood_net и support_pct.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | — | — | — |
| limit | integer | — | — |
| tier | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | — |
No examples provided.
video_classify ~172
Полный pipeline: URL -> вердикт в SQLite + Obsidian vault. ВАЖНО: долгая операция, ~10-20 мин на 300 комментов (haiku 10м + sonnet QA 8м). `qa=False` — пропустить sonnet-эскалацию (быстрее, но без QA-метрик). Возвращает verdict_id + summary (hard_counts + mood + QA-stats). На публичном сервере отключён env-флагом PJQ_PUBLIC_CLASSIFY_DISABLED=1 — синхронный classify не выдерживает параллельной нагрузки и угрожает Claude Max-подписке. Замена на job queue + worker в работе.
| Name | Type | Req | Description |
|---|---|---|---|
| qa | boolean | — | — |
| url | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
video_exemplars ~79
Exemplar-цитаты последнего снапшота по video_id. Если stance задан (SUP/AGA/NEU/OFF/THIN/SUS/AGN) — фильтруется по нему. Это единственное место, где хранится текст комментариев.
| Name | Type | Req | Description |
|---|---|---|---|
| stance | — | — | — |
| video_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | — |
No examples provided.
video_history ~51
Все снапшоты по video_id во времени (от старого к новому). Полезно для анализа динамики mood — как меняется приём со временем.
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | — |
No examples provided.
video_verdict ~99
Последний снапшот вердикта по YouTube video_id (11 симв.). Возвращает строку из verdicts + расклад в %% (из v_verdict_mood): n_sampled, cnt_* по 7 категориям, pct_*, mood_net (-1..+1), support_pct, qa_sampled_pct / qa_agreement_pct, classifier_model, rubric_version.
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | — | yes | — |
No examples provided.
videos_list ~34
Все видео из канона. Поля: id, external_id, title, channel_name, domain, tier, first_seen.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | — |
No examples provided.