SnowSignals
Registry code: 7d6e250736cb4851
SnowSignals is a market-data platform (data-as-a-service). This server exposes TrendVane — its multi-timeframe market-phase model, one of several SnowSignals data products (more, including exchange-premium feeds and partner signals, are added over time). A TrendVane 'phase' labels the current market state for a currency on a timeframe. TrendVane reports state, not a forecast or a trade signal: it names which phase the market is in, not what to do about it, so you bring your own strategy. (Signal products under SnowSignals, like the exchange-premium feeds noted above, are a different thing;…
- endpoint
- https://snowsignals.io/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 SnowSignals live?
- Yes — it answered the hub's last check (checked 15m ago). It answered 98% of checks over the last 30 days.
- Is SnowSignals free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does SnowSignals have?
- 9 tools: system_deposit_poll, trendvane_phase_resolution_stats, trendvane_list_phase_meta, trendvane_get_phase, system_get_balance, trendvane_compose_phases, system_get_usage, bfxpremium_get_premium, ….
- Is SnowSignals 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.
90 days 99%· all time 99%
last good check
of 9 tools
- down → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- down → live
- unknown → live
- used for
- get market phase for a coin
- get phases for several coins
- get bitfinex btc premium
- check prepaid balance
- takes → gives
- data → data
- tools
- 8 reads1 changes data
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.
through this hub
successful
what callers paid
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.
trendvane_phase_resolution_stats reads open 14h ago
Free, and how you read meaning into a phase. For each one it shows what usually happens next, how often a trend keeps running, and how the typical move rewarded you against how far it drew down first. Every figure comes with the number of past cases behind it. It's a behavior model built from years of Bitcoin history, not live per-coin data, so pair it with trendvane_get_phase.
{ "type": "object", "properties": {} }arguments 4 linestrendvane_list_phase_meta reads open 14h ago
The tool to call first, and it's free with no account. Lists the phases the model can report, the timeframes and currencies covered, and a short card for each phase explaining what it means and what tends to come next. Also returns the current pricing, so you can work out what a paid call costs before you make one.
{ "type": "object", "properties": {} }arguments 4 linestrendvane_get_phase reads auth-required 11h ago
Get the current market phase for one coin, across a timeframe. This is a paid call. Set `kind` to 'boundary' for the reading from the last closed bar, which is settled and won't change, or 'updates' for the live reading still forming inside the current bar. Leave `tf` off, or set it to 'all', for every timeframe.
{ "type": "object", "required": [ "currency", "kind" ], "properties": { "tf": { "enum": [ "15m", "1h", "2h", "4h", "1d", "1w", "all" ], "type": "string", "description": "Timeframe; omit or 'all' for every enabled timeframe." }, "kind": { "enum": [ "boundary", "updates" ], "type": "string", "description": "'boundary' = the settled reading from the last closed bar; 'updates' = the live reading still forming in the current bar." }, "currency": { "type": "string", "description": "The currency to classify. Call trendvane_list_phase_meta for the enabled set." } } }arguments 34 linessystem_get_balance reads auth-required 17h ago
Check your prepaid balance before a paid call. Shows the credit you have left to spend, anything on hold, any bonus credit and when it expires, whether the account is paused, the current pricing, and the deposit addresses on your account. It's free. If you run out, paid calls are turned away until you top up. To add a deposit address, sign in to the web dashboard.
{ "type": "object", "properties": {} }arguments 4 linestrendvane_compose_phases reads auth-required 11h ago
Get phases for several coins and timeframes in one paid call. Set `kind` to 'boundary' for the settled last-closed-bar reading or 'updates' for the still-forming one. The cost scales with how many readings come back, which is your coins times your timeframes.
{ "type": "object", "required": [ "currencies", "tfs", "kind" ], "properties": { "tfs": { "type": "array", "items": { "enum": [ "15m", "1h", "2h", "4h", "1d", "1w" ], "type": "string" } }, "kind": { "enum": [ "boundary", "updates" ], "type": "string", "description": "'boundary' = the settled reading from the last closed bar; 'updates' = the live reading still forming in the current bar." }, "currencies": { "type": "array", "items": { "type": "string" } } } }arguments 38 linessystem_get_usage reads auth-required 14h ago
Your history of paid calls, newest first. For each one it shows which tool you used, the coins and timeframes, how much data came back, and what it cost. Free. Page back through older calls with `before`, using the cursor the previous page returned.
{ "type": "object", "properties": { "limit": { "type": "integer", "description": "Rows per page (1–200, default 50)." }, "before": { "type": "integer", "description": "id cursor from a previous page's nextBefore (older rows)." } } }arguments 13 linesbfxpremium_get_premium reads auth-required 17h ago
Get the Bitfinex cross-exchange premium for BTC: the latest CLOSED daily residual (in basis points) and its regime state (calm, building, or stress). This is a paid call at a flat per-call price. Set `updates` to true to also append the rolling intra-day reading from the last closed sub-daily bucket; the price is the same either way. If a required exchange is unavailable the call returns an error and is not charged.
{ "type": "object", "properties": { "updates": { "type": "boolean", "description": "Set true to append the rolling intra-day reading (the last closed sub-daily bucket) to the daily reading. Defaults to false." } } }arguments 9 linessystem_get_notifications reads auth-required 17h ago
Read your account messages: support, billing, and account notices. With no arguments you get the ten most recent in each group, each with a cursor; pass a category and cursor to page further back. It's read-only and free, and it never marks anything as read. Security alerts aren't available here, and any group you've switched off for API access won't show up.
{ "type": "object", "properties": { "cursor": { "type": "string", "description": "Opaque pagination cursor from a previous nextCursor (requires category)." }, "category": { "enum": [ "support", "billing" ], "type": "string", "description": "Drill into one category." } } }arguments 17 linessystem_deposit_poll changes data unknown never probed
Call this right after you send a stablecoin deposit to have it picked up sooner: it tells the system to check your deposit addresses now. It moves no money and is free. If it comes back with nothing, you don't have a deposit address yet, so add one from the web dashboard.
{ "type": "object", "properties": {} }arguments 4 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7d6e250736cb4851.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7d6e250736cb4851/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7d6e250736cb4851?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.