Provyan MCP server
com.provyan/provyanprovyan.comstreamable-httpv1.5.0Scanned
Live crypto buy/sell pressure, whale orders, liquidations, exchange flows and tested signals.
13 tools: 10 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 9
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
10 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Provyan MCP server can do
The Provyan MCP server is published by provyan.com, a domain the MCP Registry verified. It has 13 tools. It can create or change data (10 tools: latest_signals, whale_orders, whale_wallets, liquidation_levels and 6 more), but cannot delete data. 3 tools only read.
9 tools bring in text other people can write (whale_orders, whale_wallets, liquidation_levels and 6 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.5.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 10Claude Code: ask
indicator_scoreboardNineteen market indicators (order-book imbalance, market and whale order flow, liquidations, whale-wallet positions, funding, futures premium, top traders' ratio, open interest, ex…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Nineteen market indicators (order-book imbalance, market and whale order flow, liquidations, whale-wallet positions, funding, futures premium, top traders' ratio, open interest, exchange flows, bid-ask spread) graded against what the price did in the 15 minutes after each reading, from a minute-by-minute record of BTC, ETH, SOL, XRP, DOGE and HYPE that is graded again every hour. Each indicator gets a verdict: price followed it, price went against it, or no steady link. It also returns the combined reading per coin right now and its sealed record: that reading written down at the top of every hour before the outcome, chained by SHA-256, with how often the price then moved its way after 15 minutes and after an hour. Answers "which crypto indicators actually work right now", "does funding rate predict price" and "is order-book imbalance a reliable signal". Live market data, not advice.
Annotations the server declares
- title: Which indicators the price is following
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
latest_signalsSignals 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 hi…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Latest revealed signals
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
liquidation_levelsWhere leveraged long and short positions in a coin would be liquidated: the dollar value at risk within 2%, 5% and 10% below and above the current price, and the heaviest level on …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Where leveraged long and short positions in a coin would be liquidated: the dollar value at risk within 2%, 5% and 10% below and above the current price, and the heaviest level on each side, estimated from hourly futures open interest. Covers sixty major coins. Answers "where are the BTC liquidation levels" and "which side has more to lose on ETH". Live market data, not advice.
Annotations the server declares
- title: Liquidation levels for a coin
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
liquidation_priceThe price at which a leveraged long or short would be liquidated, from entry price and leverage, with isolated margin.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The price at which a leveraged long or short would be liquidated, from entry price and leverage, with isolated margin. Name a coin to use its live price as the entry and to get its funding rate and the heaviest levels on that coin's liquidation map beside the answer, so the position can be judged against where the crowd would be closed. Answers "where is my liquidation price on a 20x long from 60,000" and "how far is liquidation on a 10x ETH short opened now".
Annotations the server declares
- title: Liquidation price of a leveraged position
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
live_alertsThe latest market alerts Provyan sent to its members: turns in buy or sell pressure, liquidation waves, whale-wallet events and large exchange transfers, each as one plain sentence…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The latest market alerts Provyan sent to its members: turns in buy or sell pressure, liquidation waves, whale-wallet events and large exchange transfers, each as one plain sentence with its time. Answers "what just happened in the crypto market" and "any whale alerts in the last hour". Live market data, not advice.
Annotations the server declares
- title: Latest market alerts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
live_liquidationsReal forced liquidations on perpetual futures as they happen: dollar totals of longs and shorts closed by force over the last hour, 4 hours and 24 hours, the coins hit hardest, and…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Real forced liquidations on perpetual futures as they happen: dollar totals of longs and shorts closed by force over the last hour, 4 hours and 24 hours, the coins hit hardest, and the largest single liquidations with price and venue. Answers "how much was liquidated in the last hour", "are longs or shorts being wiped out" and "biggest liquidation today". Live market data, not advice.
Annotations the server declares
- title: Liquidations happening now
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
market_pressureWhere large traders are leaning right now, as one number per coin from −100 (selling) to +100 (buying), recalculated every minute from large orders over one and four hours, the pos…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Where large traders are leaning right now, as one number per coin from −100 (selling) to +100 (buying), recalculated every minute from large orders over one and four hours, the positions of the biggest Hyperliquid traders and forced liquidations. For BTC, ETH and SOL it also returns the sealed hourly record: every reading written down before the outcome and the price four hours later. Answers "is BTC under buy or sell pressure right now", "which way are whales leaning on ETH" and "how often was the reading followed". Live market data, not advice.
Annotations the server declares
- title: Buy and sell pressure now
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
onchain_movesLarge transfers of BTC, ETH, USDT and USDC read block by block from the Bitcoin and Ethereum networks, with the exchange named when a known exchange wallet is on either side, plus …Reads text others write1 finding
Why it is in this group
- The name "onchain_moves" says "move": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "onchain_moves" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "onchain_moves" says "move": a word for a change.
Description, as the server wrote it Large transfers of BTC, ETH, USDT and USDC read block by block from the Bitcoin and Ethereum networks, with the exchange named when a known exchange wallet is on either side, plus each exchange's money in, money out and net flow over 24 hours. With an exchange named, that exchange's own inflow, outflow and net flow per asset and its latest transfers. Answers "did whales just move bitcoin to an exchange", "which exchange saw the biggest inflow today", "what is Binance's net flow today" and "any large USDT transfers in the last hour". Live market data, not advice.
Annotations the server declares
- title: Large on-chain transfers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
whale_ordersThe latest large crypto market orders (whale trades) caught as they trade on Binance, OKX, Gate and Hyperliquid in sixty major coins, with value, average price and side, plus how m…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The latest large crypto market orders (whale trades) caught as they trade on Binance, OKX, Gate and Hyperliquid in sixty major coins, with value, average price and side, plus how much large buying and large selling each coin saw in the last 24 hours. Filter by coin and by smallest order in dollars. Answers "what are whales buying or selling right now" and "any large BTC orders in the last hour". Live market data, not advice.
Annotations the server declares
- title: Latest whale orders
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
whale_walletsThe Hyperliquid wallets behind the largest orders of the last two days and what each holds now: coin, long or short, position value, entry price, leverage, liquidation price and un…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The Hyperliquid wallets behind the largest orders of the last two days and what each holds now: coin, long or short, position value, entry price, leverage, liquidation price and unrealized profit or loss, read from the chain. Answers "what are the biggest Hyperliquid traders holding" and "is that whale in profit". Live market data, not advice.
Annotations the server declares
- title: Whale wallets and their positions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
find_evidenceLists the coin-and-signal studies with the strongest historical evidence, best first.No findings
Why it is in this group
- The name "find_evidence" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find the strongest studies
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_studyWhat historically happened to a crypto coin's price after a specific signal (e.g.No findings
Why it is in this group
- The name "get_study" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one signal study
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_coins_and_signalsThe coins and signal ids Provyan studies, with each signal's exact rule.No findings
Why it is in this group
- The name "list_coins_and_signals" says "list": a word for reading.
Description, as the server wrote it The coins and signal ids Provyan studies, with each signal's exact rule.
Annotations the server declares
- title: List coins and signals
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write9
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://provyan.com/mcp: tools/list returned 4 tools to an anonymous client, including latest_signals (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnonchain_moves
The server marks "onchain_moves" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "onchain_moves" says "move": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 4 changed.+1 added~4 changedView diff
- Added:indicator_scoreboardChanges things
- Changed:liquidation_levelsChanges thingsdescription
- Changed:liquidation_priceChanges thingsinputSchema
- Changed:onchain_movesChanges thingsdescriptioninputSchema
- Changed:whale_ordersChanges thingsdescription
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:liquidation_priceChanges things
- Changed:whale_ordersChanges thingsdescription
Tools4 added.+4 addedView diff
- Added:live_alertsChanges things
- Added:live_liquidationsChanges things
- Added:market_pressureChanges things
- Added:onchain_movesChanges things
Tools3 added.+3 addedView diff
- Added:liquidation_levelsChanges things
- Added:whale_ordersChanges things
- Added:whale_walletsChanges things
Install
Pinned to version 1.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http provyan https://provyan.com/mcpclaude mcp add --transport http provyan https://provyan.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__provyan__get_study",
"mcp__provyan__find_evidence",
"mcp__provyan__list_coins_and_signals"
],
"ask": [
"mcp__provyan__latest_signals",
"mcp__provyan__whale_orders",
"mcp__provyan__whale_wallets",
"mcp__provyan__liquidation_levels",
"mcp__provyan__liquidation_price",
"mcp__provyan__market_pressure",
"mcp__provyan__live_liquidations",
"mcp__provyan__onchain_moves",
"mcp__provyan__indicator_scoreboard",
"mcp__provyan__live_alerts"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as provyan. Review it before you use it.
Capability tags behind 9 rules
- mcp__provyan__whale_orders untrusted-input
- mcp__provyan__whale_wallets untrusted-input
- mcp__provyan__liquidation_levels untrusted-input
- mcp__provyan__liquidation_price untrusted-input
- mcp__provyan__market_pressure untrusted-input
- mcp__provyan__live_liquidations untrusted-input
- mcp__provyan__onchain_moves untrusted-input
- mcp__provyan__indicator_scoreboard untrusted-input
- mcp__provyan__live_alerts untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.provyan/provyan/verify?hash=1a8b72f208062eaac0e4fa11653ebfe63ac973d4aefe179d6562b4e61dadc8ed" | jq -e '.changed == false'Pinned hash 1a8b72f20806, from Nov 21, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.provyan/provyan/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.provyan/provyan)Source: MCP Registry. Synced Nov 21, 2026, 00:17 UTC.
Provyan MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Provyan MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 10 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Provyan MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Provyan MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Provyan MCP server have?
- 13 tools: 10 write, 3 read. latest_signals, whale_orders, whale_wallets, liquidation_levels, liquidation_price, market_pressure, live_liquidations, onchain_moves and 5 more.
Does the Provyan MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Provyan MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Provyan MCP server changed its tools?
- Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.