PRUVIQ strategy verdicts (read-only)
REMOTE · PRUVIQ.COM
Read-only crypto strategy backtest & verification verdicts. No trading tools; every result is cited.
Available components
Last scanned (19 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Server version: 1.0.0 → 1.1.0 functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +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.
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 26 Oct 26 +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.
- 25 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 23 Oct 26 +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.
- 21 Oct 26 +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.
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 5 Nov 2026 · Probed https://pruviq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pruviq.com | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a1b3d831f865a7181366bc17e86fa280 |
| SANs: pruviq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pruviq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| pruviq.com. | No DS | 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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pruviq.com/mcp | Verified | 200 | |
| http (plaintext) | http://pruviq.com/mcp | HTTPS enforced | 301 | https://pruviq.com/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_coin_strategy_stats Get per-strategy backtest stats for one coin ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Coin symbol: BTC, BTCUSDT, BTC-USDT-SWAP. |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
No examples provided.
get_daily_rankings Get the daily strategy ranking ~117
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
No examples provided.
get_forward_verification_records Get forward-test pre-registration and timestamp proofs ~53
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
No examples provided.
get_methodology Explain the methodology and how to re-verify ~58
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
No examples provided.
get_strategy_verdict Get one strategy's verdict ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| strategy_id | string | yes | Strategy id as returned by list_strategies, e.g. "bb-squeeze-long". |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
No examples provided.
list_strategies List strategies with research status ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Only return strategies with this research status. |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
No examples provided.
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.
remote · pruviq.com
claude mcp add --transport http com-pruviq-verdicts 'https://pruviq.com/mcp'
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.