Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"life-pjq-pjq": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A seismograph for public opinion. PJQ measures how an audience actually > received a piece of media — separating genuine opinion from fan noise, bots,
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
MCP Security Weekly
Get CVE alerts and security updates for life.pjq/pjq and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
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:
/api/v1/*) for analytics automation, and/mcp/) so AI agents (Claude Desktop and friends) can run
analyses and read verdicts directly inside a chat.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)
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.
The client is a standard Vite SPA. By default it talks to the hosted backend at
pjq.life (same-origin in production).
cd web
npm install
npm run dev # dev server with hot reload
npm 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.
docs/api-reference.md. Read-only tools cost
no credits; a full analysis costs one credit.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.
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.
Copyright 2026 PJQ (github.com/Makaric). Licensed under the Apache License,
Version 2.0 — see LICENSE.
Русская версия: README_RU.md.