_ registry / mcp streamable-http · checked 2h ago

pruviq-verdicts

https://pruviq.com

Registry code: 3aba8ac788501c4d

api record

PRUVIQ publishes backtest and verification results for crypto trading strategies. There is no single market scope for everything: each result's citation.data_scope states the market, data source, population and costs of that answer, as the site publishes them for the source file. Strategy-page headline figures carry their own scope (the page's original backtest, not re-measured; data_era says what the record states about Binance-era candles).

Use these tools BEFORE acting on a strategy: a high backtest number is not a verification. Read `verdict.tone` and `verdict.why` from…

endpoint
https://pruviq.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pruviq-verdicts live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is pruviq-verdicts free to use?
Yes — the hub reached it with no key and no payment.
What tools does pruviq-verdicts have?
6 tools: get_strategy_verdict, get_coin_strategy_stats, get_methodology, get_daily_rankings, get_forward_verification_records, list_strategies.
Is pruviq-verdicts safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.6%

90 days 98.4%· all time 98.4%

latency
164ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 322 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • check verdict on a crypto trading strategy
  • get backtest stats for a coin
  • get daily strategy rankings
  • get forward verification records
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
4 open 2 never probed 4 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_methodology reads open 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_daily_rankings reads open 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_forward_verification_records reads open 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_strategies reads open 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "status": {
          "enum": [
            "verified",
            "conditional",
            "testing",
            "live",
            "shelved",
            "killed"
          ],
          "type": "string",
          "description": "Only return strategies with this research status."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_strategy_verdict reads unknown 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "strategy_id"
      ],
      "properties": {
        "strategy_id": {
          "type": "string",
          "pattern": "^[a-z0-9-]{1,64}$",
          "description": "Strategy id as returned by list_strategies, e.g. \"bb-squeeze-long\"."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_coin_strategy_stats reads unknown 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "maxLength": 32,
          "minLength": 1,
          "description": "Coin symbol: BTC, BTCUSDT, BTC-USDT-SWAP."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3aba8ac788501c4d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3aba8ac788501c4d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3aba8ac788501c4d/badge.svg)](https://brick.blue/agent/3aba8ac788501c4d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.