_ registry / mcp http-sse · checked 1h ago

net.polysignals/polysignals

https://polysignals.net

Registry code: 8ddf825631cc74be

api record

PolySignals.net reads crypto Up/Down prediction markets (Polymarket, Kalshi, Limitless, Gemini) and options (Binance, Deribit, Bybit, OKX) and publishes one Buy / Sell / Hold reading per coin and window (5m to 1d) with a 0-100 confidence, a daily regime (trend) call per coin, and a live backtest of following the calls. Start with get_overview for every coin, get_coin_signal for one coin; get_trend_changes lists the coins whose daily trend call recently turned long or flat (the signals sent to Cryptohopper), get_signal_markets the exchange markets on Cryptohopper those signals go to; get_news…

endpoint
https://polysignals.net/api/mcp
protocol
http-sse ·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 net.polysignals/polysignals live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is net.polysignals/polysignals free to use?
Yes — the hub reached it with no key and no payment.
What tools does net.polysignals/polysignals have?
10 tools: get_coin_signal, get_trend_changes, get_signal_markets, get_results, get_history, list_coins_and_venues, get_methodology, get_news, ….
Is net.polysignals/polysignals 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
363ms

last good check

priced tools
0

of 10 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 10 tools
3 open 7 never probed 3 of 10 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_news open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Only headlines naming this coin"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    }
  }
}
    arguments 18 lines
  • get_overview open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_regime open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Coin ticker or name as on the site, for example BTC, ETH or SOL"
    }
  }
}
    arguments 12 lines
  • get_coin_signal unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "coin"
  ],
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Coin ticker or name as on the site, for example BTC, ETH or SOL"
    },
    "timeframe": {
      "enum": [
        "5m",
        "15m",
        "1h",
        "4h",
        "1d"
      ],
      "type": "string",
      "description": "Only this window"
    }
  }
}
    arguments 26 lines
  • get_trend_changes unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Only this coin, for example SOL: its current trend call and when it last changed"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 30,
      "minimum": 1,
      "description": "Decisions to list"
    }
  }
}
    arguments 19 lines
  • get_signal_markets unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Only this coin, for example SOL"
    },
    "exchange": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1,
      "description": "Cryptohopper exchange by name or key, for example Binance, Kraken, OKX, Coinbase or kraken2"
    }
  }
}
    arguments 18 lines
  • get_results unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Coin ticker or name as on the site, for example BTC, ETH or SOL"
    },
    "strategy": {
      "enum": [
        "5m",
        "15m",
        "1h",
        "4h",
        "1d",
        "overall",
        "regime",
        "regime_4h"
      ],
      "type": "string",
      "description": "Default regime; ignored when a coin is given"
    }
  }
}
    arguments 26 lines
  • get_history unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "coin"
  ],
  "properties": {
    "coin": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Coin ticker or name as on the site, for example BTC, ETH or SOL"
    },
    "hours": {
      "type": "integer",
      "default": 6,
      "maximum": 48,
      "minimum": 1
    },
    "timeframe": {
      "enum": [
        "5m",
        "15m",
        "1h",
        "4h",
        "1d"
      ],
      "type": "string",
      "default": "1h"
    }
  }
}
    arguments 32 lines
  • list_coins_and_venues unknown never probed

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

    mcp-tool

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

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "section": {
      "type": "string",
      "maxLength": 100,
      "description": "A section title or part of one, for example 'confidence' or 'regime'"
    }
  }
}
    arguments 11 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 8ddf825631cc74be.

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