# io.github.OnChainAIIntel/pqs-mcp-server (remote · promptqualityscore.com)

PQS scores any prompt before the model runs. 8 dimensions. 5 frameworks. Pre-flight, not post-hoc.

- Trust score: 60/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `promptqualityscore.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/api-mcp.md), [page](https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/api-mcp)
- npm · `pqs-mcp-server`: 65/100, [markdown](https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/pqs-mcp-server.md), [page](https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/pqs-mcp-server)

## Channel facts

- Endpoint: `https://promptqualityscore.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 736 tokens (~368/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http onchainaiintel-pqs-mcp-server https://promptqualityscore.com/api/mcp
```

### Codex

```toml
[mcp_servers.onchainaiintel-pqs-mcp-server]
url = "https://promptqualityscore.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "onchainaiintel-pqs-mcp-server": {
      "type": "remote",
      "url": "https://promptqualityscore.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add onchainaiintel-pqs-mcp-server --url https://promptqualityscore.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  onchainaiintel-pqs-mcp-server:
    url: "https://promptqualityscore.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "onchainaiintel-pqs-mcp-server": {
      "type": "http",
      "url": "https://promptqualityscore.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 56, +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.

### 2026-07-27 (score 55, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (2)

### `score_prompt` (~310 tokens)

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.

Input parameters:

- `prompt` (string, required): The prompt text to score. Single prompt, not a conversation. Max 8000 characters.

### `optimize_prompt` (~426 tokens)

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.

Input parameters:

- `api_key` (string): PQS API key from a Pro subscription. Required. Format: pqs_live_… (32+ characters). Subscribe at https://promptqualityscore.com/pricing?utm_source=mcp&utm_medium=schema_description_v140&utm_campaign=…
- `prompt` (string, required): The prompt to optimize. Max 8000 characters.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/api-mcp#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 57
- 2026-07-29: 56
- 2026-07-28: 56
- 2026-07-27: 55
- 2026-07-26: 54

## Links

- Remote endpoint: https://promptqualityscore.com/api/mcp
- Repository: https://github.com/OnChainAIIntel/pqs-mcp-server
- Website: https://promptqualityscore.com/
- Changelog RSS feed: https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/onchainaiintel-pqs-mcp-server/api-mcp