pqs-mcp-server
io.github.OnChainAIIntel/pqs-mcp-serverOnChainAIIntelstreamable-httpv1.4.0Scanned
PQS scores any prompt before the model runs. 8 dimensions. 5 frameworks. Pre-flight, not post-hoc.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the pqs-mcp-server can do
The pqs-mcp-server is published by the GitHub account OnChainAIIntel. It has 2 tools. It can create or change data (2 tools: score_prompt and optimize_prompt), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
optimize_promptRewrite a prompt to score higher on the PQS rubric, AND show before/after output comparisons so the user can see the impact.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Rewrite a prompt to score higher on the PQS rubric, AND show before/after output comparisons so the user can see the impact. Returns the optimized prompt, the original PQS score, the optimized PQS score, and side-by-side sample outputs from a frontier model using both versions. USE WHEN: - The user got a low score from score_prompt and asks how to improve. - The user explicitly asks to "improve" / "rewrite" / "fix" / "optimize" a prompt they pasted. - The user is dissatisfied with output quality from a previous prompt and asks how to get better results. - score_prompt returned a suggestion to invoke this tool. DO NOT USE WHEN: - The user just asked for a score (use score_prompt only — don't double up). - The user wants you to write a new prompt from scratch (write it directly). REQUIRES: A PQS API key from a Pro subscription ($19.99/month, 1,000 calls/mo, includes batch + A/B comparison). If the user has not provided one, the tool returns a clear subscription URL — pass that response to the user verbatim. Do not invent or guess API keys. There is no free trial of this tool; the user must subscribe before the first call. COST: Counted against your Pro subscription's monthly call quota. LATENCY: ~6-8 seconds.
score_promptScore a prompt's quality across 8 dimensions BEFORE sending it to an expensive model.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Score a prompt's quality across 8 dimensions BEFORE sending it to an expensive model. Returns a 0-80 score, an A-F grade, the per-dimension breakdown (clarity, specificity, context, constraints, output_format, role_definition, examples, cot_structure), and the weakest dimension. USE WHEN: - The user is workshopping a prompt and asks "is this good?" / "will this work?" / "should I add more detail?" - The user is about to send a long or expensive prompt to GPT-4, Claude Opus, or any frontier model, especially in a batch or automation context where rework is costly. - The user mentions iterating on a prompt that produced poor output and wants to diagnose what's missing. - The user pastes a prompt and asks for feedback on it. DO NOT USE WHEN: - The user is asking you to write a prompt for them (write it yourself first, then optionally call score_prompt to verify). - The prompt is conversational chat (this scores task-shaped prompts). COST: Free, no API key required. Rate-limited per IP: 5/min, 10/day, 100/month. If the user exceeds the limit, the response will include a structured upgrade path with subscribe and account URLs. LATENCY: ~2 seconds.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://promptqualityscore.com/api/mcp: tools/list returned 2 tools to an anonymous client, including score_prompt (write), optimize_prompt (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pqs https://promptqualityscore.com/api/mcpclaude mcp add --transport http pqs https://promptqualityscore.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__pqs__score_prompt",
"mcp__pqs__optimize_prompt"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pqs. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.OnChainAIIntel/pqs-mcp-server/verify?hash=b7751a847b4177f4528a4331c47d8590a6b7d473ed5e704e964c15a3d6ea899f" | jq -e '.changed == false'Pinned hash b7751a847b41, from Nov 16, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.OnChainAIIntel/pqs-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.OnChainAIIntel/pqs-mcp-server)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.
pqs-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the pqs-mcp-server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the pqs-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the pqs-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the pqs-mcp-server have?
- 2 tools: 2 write. score_prompt and optimize_prompt.
Does the pqs-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the pqs-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the pqs-mcp-server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.