_ registry / mcp streamable-http · checked 13m ago

Provyan

https://provyan.com

Registry code: 3fd7d2e3d95471e7

api record

Provyan tests crypto trading signals against history. find_evidence lists what has held up, get_study covers one coin and one signal, latest_signals is the live sealed record. Every result is a statistic about the past, with its source page on https://provyan.com; none is advice or a prediction.

endpoint
https://provyan.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 Provyan live?
Yes — it answered the hub's last check (checked 13m ago). It answered 100% of checks over the last 30 days.
Is Provyan free to use?
Yes — the hub reached it with no key and no payment.
What tools does Provyan have?
4 tools: latest_signals, list_coins_and_signals, get_study, find_evidence.
Is Provyan 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
100%

90 days 100%· all time 100%

latency
929ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • find_evidence open 13m ago

    Lists the coin-and-signal studies with the strongest historical evidence, best first. Filter by coin, by signal, by lean (bullish or bearish) and by minimum proof score (default 55). Answers questions such as "which crypto signals actually worked" or "what has worked on <coin>". Statistics about past price behaviour on Binance daily candles. Not financial advice and not a prediction.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "coin": {
      "type": "string"
    },
    "lean": {
      "enum": [
        "bullish",
        "bearish"
      ],
      "type": "string"
    },
    "limit": {
      "type": "number"
    },
    "signal": {
      "type": "string"
    },
    "min_score": {
      "type": "number"
    }
  }
}
    arguments 24 lines
  • latest_signals unknown never probed

    Signals recently detected and publicly revealed in Provyan's hash-chained ledger, with the call made at the time and the graded result once seven days have passed, plus the live hit record. Statistics about past price behaviour on Binance daily candles. Not financial advice and not a prediction.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_coins_and_signals unknown never probed

    The coins and signal ids Provyan studies, with each signal's exact rule.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_study unknown 13m ago

    What historically happened to a crypto coin's price after a specific signal (e.g. RSI oversold, a 20% weekly drop, a breakout), measured on every past occurrence and compared with the coin's ordinary days. Returns case count, win rate, median move before and after trading costs, typical dip on the way, the luck probability after multiple-testing correction, and a 0-100 proof score. Statistics about past price behaviour on Binance daily candles. Not financial advice and not a prediction.

    mcp-tool

    {
  "type": "object",
  "required": [
    "coin",
    "signal"
  ],
  "properties": {
    "coin": {
      "type": "string",
      "description": "Ticker or slug, e.g. BTC or bitcoin"
    },
    "signal": {
      "type": "string",
      "description": "Signal id, e.g. rsi-oversold, weekly-drop-20, golden-cross"
    }
  }
}
    arguments 17 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 3fd7d2e3d95471e7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3fd7d2e3d95471e7/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/3fd7d2e3d95471e7/badge.svg)](https://brick.blue/agent/3fd7d2e3d95471e7?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
80%

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.