Skip to content
anlyon.devby Anlyon

PolySignals.net

net.polysignals/polysignalspolysignals.netstreamable-httpv1.0.0Scanned

Live crypto Buy/Sell/Hold readings from prediction markets and options, plus daily trend calls.

10 tools: 10 only read.

Tools: 0 delete, 0 irreversible, 0 write, 10 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

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.

10 tools

Only reads 10Show 10 read-only tools
  • get_coin_signalOne 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,…No findings

    Why it is in this group

    • The name "get_coin_signal" says "get": a word for reading.
    Description, as the server wrote it
    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 regime call, the Cryptohopper markets that get its signals and its latest delivery, the live backtest, and the newest headlines that name it. Pass timeframe to narrow it to one window.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_historyThe 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.No findings

    Why it is in this group

    • The name "get_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_methodologyThe methodology document: what the score is, confidence, window matching, options readings, the backtest and the daily regime rule.Reads private dataNo findings

    Why it is in this group

    • The name "get_methodology" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_newsThe latest crypto headlines from CoinArticle, newest first, each with the live overall Buy/Sell/Hold call of every tracked coin it names.Reads text others writeNo findings

    Why it is in this group

    • The name "get_news" says "get": a word for reading.

    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 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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_overviewEvery 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).Reads private dataNo findings

    Why it is in this group

    • The name "get_overview" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "table": it reads databases.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_regimeThe 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.No findings

    Why it is in this group

    • The name "get_regime" says "get": a word for reading.
    Description, as the server wrote it
    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 call, distance, days in state and the close that would change it.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_resultsWhat 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 th…No findings

    Why it is in this group

    • The name "get_results" says "get": a word for reading.
    Description, as the server wrote it
    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: the daily regime) for every coin; with a coin: all eight strategies.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_signal_marketsWhich 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, …No findings

    Why it is in this group

    • The name "get_signal_markets" says "get": a word for reading.
    Description, as the server wrote it
    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 its coin and market counts; with exchange: its markets per coin; with coin: that coin's markets on every exchange; with both: that one list.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_trend_changesThe 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 da…No findings

    Why it is in this group

    • The name "get_trend_changes" says "get": a word for reading.
    Description, as the server wrote it
    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 live price is closest to the level that would change their call, how many Cryptohopper markets accepted each recent signal, and how many coins were long after each daily close over the last 90 days. A coin's starting call is not listed as a change. Give a coin for that coin alone: its current call, since when, whether it began as a change, and its calls over the last 90 closes.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_coins_and_venuesWhich coins have venue readings, the windows, and each venue with its type and how many coins it covers.No findings

    Why it is in this group

    • The name "list_coins_and_venues" says "list": a word for reading.
    Description, as the server wrote it
    Which coins have venue readings, the windows, and each venue with its type and how many coins it covers.

    Annotations the server declares

    • readOnlyHint: 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 outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http polysignals https://polysignals.net/api/mcp
claude mcp add --transport http polysignals https://polysignals.net/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__polysignals__get_overview",
      "mcp__polysignals__get_coin_signal",
      "mcp__polysignals__get_regime",
      "mcp__polysignals__get_trend_changes",
      "mcp__polysignals__get_signal_markets",
      "mcp__polysignals__get_results",
      "mcp__polysignals__get_history",
      "mcp__polysignals__list_coins_and_venues",
      "mcp__polysignals__get_methodology",
      "mcp__polysignals__get_news"
    ],
    "ask": [],
    "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 polysignals. Review it before you use it.

Capability tags behind 3 rules
  • mcp__polysignals__get_overview private-data
  • mcp__polysignals__get_methodology private-data
  • mcp__polysignals__get_news 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://anlyon.dev/api/v1/servers/net.polysignals/polysignals/verify?hash=7b4521844356b12b4b75ca94508a445c7e33efda1b37d084669c8495c324366e" | jq -e '.changed == false'

Pinned hash 7b4521844356, from Oct 28, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/net.polysignals/polysignals/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for net.polysignals/polysignals
[![anlyon.dev](https://anlyon.dev/badge/net.polysignals/polysignals.svg)](https://anlyon.dev/servers/net.polysignals/polysignals)

Source: MCP Registry. Synced Oct 28, 2026, 14:18 UTC.