# PRUVIQ strategy verdicts (read-only) (remote · pruviq.com)

Read-only crypto strategy backtest & verification verdicts. No trading tools; every result is cited.

- Trust score: 87/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `pruviq.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-pruviq-verdicts/pruviq.md), [page](https://verifymcp.io/servers/com-pruviq-verdicts/pruviq)

## Channel facts

- Endpoint: `https://pruviq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 849 tokens (~141/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the PRUVIQ strategy verdicts (read-only) MCP server?

PRUVIQ strategy verdicts (read-only) is a hosted endpoint at https://pruviq.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-pruviq-verdicts 'https://pruviq.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-pruviq-verdicts": {
      "url": "https://pruviq.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pruviq-verdicts": {
      "type": "http",
      "url": "https://pruviq.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-pruviq-verdicts]
url = "https://pruviq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pruviq-verdicts": {
      "type": "remote",
      "url": "https://pruviq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pruviq-verdicts --url 'https://pruviq.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pruviq-verdicts:
    url: "https://pruviq.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-pruviq-verdicts": {
      "Transport": "http",
      "Url": "https://pruviq.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pruviq-verdicts -t streamable-http -u 'https://pruviq.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-pruviq-verdicts": {
      "type": "http",
      "url": "https://pruviq.com/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-11-05 (score 87, 0)

- [functional] Server version: 1.0.0 → 1.1.0

### 2026-11-01 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 87, +1)

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

### 2026-10-28 (score 86, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-26 (score 85, +1)

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

### 2026-10-25 (score 84, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-23 (score 84, +1)

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

### 2026-10-21 (score 83, +1)

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

## MCP tools (6)

### `list_strategies` (~97 tokens)

List strategies with research status

List every strategy PRUVIQ publishes, with its research status (verified / conditional / testing / live / shelved / killed), the simulator preset verdict, headline metrics as the strategy page shows them (original backtest, not re-measured — see each row's headline_scope), and the URL of the full record. Optional filter by status. Read-only.

Input parameters:

- `status` (string): Only return strategies with this research status.

Output parameters:

- `citation` (object)

### `get_strategy_verdict` (~114 tokens)

Get one strategy's verdict

Get the published verdict for one strategy: tone (verified / caution / negative, or no_definition) and the reasons, re-measured metrics and the strategy page's headline metrics (each block with its own scope), measurement date, sample size (trades), fees included in the measurement, verification record and how to reproduce it. Use before acting on any backtest number. Read-only.

Input parameters:

- `strategy_id` (string, required): Strategy id as returned by list_strategies, e.g. "bb-squeeze-long".

Output parameters:

- `citation` (object)

### `get_daily_rankings` (~117 tokens)

Get the daily strategy ranking

Get PRUVIQ's published daily ranking snapshot: the headline (headline_slots: up to 3 configurations labelled verified, in ranking order with their full-ranking rank; empty slots say no verified setting), the best (top3 = PF-ordered research record across all statuses, not the headline) and worst configurations by backtest over the published window, each with its research status, sample size and low-sample flag, plus the headline note about whether any verified configuration is ranked. A rank is not a verification. Read-only.

Output parameters:

- `citation` (object)

### `get_coin_strategy_stats` (~100 tokens)

Get per-strategy backtest stats for one coin

Get per-strategy backtest statistics (trades, win rate, profit factor, total return, exit reasons, data window) for one OKX USDT-SWAP perpetual, e.g. "BTC", "BTCUSDT" or "BTC-USDT-SWAP". Cells below the minimum sample are flagged. Read-only.

Input parameters:

- `symbol` (string, required): Coin symbol: BTC, BTCUSDT, BTC-USDT-SWAP.

Output parameters:

- `citation` (object)

### `get_methodology` (~58 tokens)

Explain the methodology and how to re-verify

Explain how PRUVIQ measures and labels strategies (ranking criteria, research status definitions, verification criteria version, research-ledger arbiter and cost) and give the exact steps and public tools to re-verify a claim yourself. Read-only.

Output parameters:

- `citation` (object)

### `get_forward_verification_records` (~53 tokens)

Get forward-test pre-registration and timestamp proofs

Get the forward (out-of-sample, real-time) verification program records: pre-registration files with sha256, OpenTimestamps proof state (bitcoin block heights), program status and verdict dates. Read-only.

Output parameters:

- `citation` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pruviq-verdicts/pruviq#diagnostics

## Score history

- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 87
- 2026-10-31: 87
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 86
- 2026-10-27: 85
- 2026-10-26: 85
- 2026-10-25: 84
- 2026-10-24: 84
- 2026-10-23: 84
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 82
- 2026-10-19: 82
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 80
- 2026-10-14: 80
- 2026-10-13: 79
- 2026-10-12: 79
- 2026-10-10: 78
- 2026-10-09: 77
- 2026-10-06: 76
- 2026-10-04: 75
- 2026-10-03: 75

## Common questions

### What is the PRUVIQ strategy verdicts (read-only) MCP server?

PRUVIQ strategy verdicts (read-only) is an MCP server listed in the public MCP registry as com.pruviq/verdicts. Read-only crypto strategy backtest & verification verdicts. No trading tools; every result is cited. This page covers its hosted endpoint (https://pruviq.com/mcp).

### Is the PRUVIQ strategy verdicts (read-only) MCP server safe to use?

PRUVIQ strategy verdicts (read-only) scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the PRUVIQ strategy verdicts (read-only) MCP server expose?

PRUVIQ strategy verdicts (read-only) exposes 6 tools: list_strategies, get_strategy_verdict, get_daily_rankings, get_coin_strategy_stats, get_methodology, get_forward_verification_records. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.

### Does the PRUVIQ strategy verdicts (read-only) MCP server require authentication?

No. We connected to PRUVIQ strategy verdicts (read-only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PRUVIQ strategy verdicts (read-only) MCP server still maintained?

PRUVIQ strategy verdicts (read-only) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the PRUVIQ strategy verdicts (read-only) MCP server?

VerifyMCP ran 13 checks on PRUVIQ strategy verdicts (read-only), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pruviq.com/mcp
- Website: https://pruviq.com/methodology/
- Changelog RSS feed: https://verifymcp.io/servers/com-pruviq-verdicts/pruviq.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pruviq-verdicts/pruviq/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-pruviq-verdicts/pruviq.json
- HTML version of this page: https://verifymcp.io/servers/com-pruviq-verdicts/pruviq