Cryptohopper MCP server

• Registry namenet.polysignals/polysignalsverified in the MCP registry

The registry name sits under polysignals.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-29
• Tools10
• Server calls itselfnet.polysignals/polysignals
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 690 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer720 ms
• Space in an agent's context≈ 1,497 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsA · 97 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 2 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_overview

  Every tracked coin in one table: spot price, the overall Buy/Sell/Hold call with score and confidence, the 1 hour window, and the daily regime call (long or flat).

• get_coin_signal

  One coin in full: the overall call, each window running now (5m, 15m, 1h, 4h, 1d) blended across venues with score, up probability, confidence and the move since the window opened, the next windows, each venue's own reading, the daily…

• get_regime

  The daily regime (trend) rule relayed to Cryptohopper: long while the Coinbase daily close is more than one 20-day sigma above its 50-day average, flat once more than one below. Without a coin: the board for every coin; with a coin: its…

• get_trend_changes

  The coins whose daily trend (regime) call changed, newest decision first: turned long (sent to Cryptohopper as a buy signal) or turned flat (a sell), decided at 00:05 UTC on the daily close, plus the next decision time, the coins whose…

• get_signal_markets

  Which exchange markets on Cryptohopper receive the daily trend signals (buy when a coin turns long, sell when it turns flat), in each exchange's own market format such as BTCUSDT, XBT/EUR or BTC-USD. Without arguments: every exchange with…

• get_results

  What following the calls would have returned, trading the coin against USD on Coinbase with fees, next to buy and hold: net and gross return, round trips, win rate, drawdown and the current position. Without a coin: one strategy (default…

• get_history

  The blended reading of one coin's window over the last hours (up to 48), thinned to about 36 rows: time, up probability, score and confidence.

• list_coins_and_venues

  Which coins have venue readings, the windows, and each venue with its type and how many coins it covers.

• get_methodology

  The methodology document: what the score is, confidence, window matching, options readings, the backtest and the daily regime rule. Without a section: the list of sections and the introduction; with one: that section.

• get_news

  The latest crypto headlines from CoinArticle, newest first, each with the live overall Buy/Sell/Hold call of every tracked coin it names. Pass coin to keep only headlines that name it.