# io.snowsignals/snowsignals (remote · snowsignals.io)

Market-phase classifications over a metered API — phase events per currency and timeframe.

- Trust score: 78/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `snowsignals.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-snowsignals-snowsignals/snowsignals.md), [page](https://verifymcp.io/servers/io-snowsignals-snowsignals/snowsignals)

## Channel facts

- Endpoint: `https://snowsignals.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1503 tokens (~167/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 18 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 9 additions.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.snowsignals/snowsignals MCP server?

io.snowsignals/snowsignals is a hosted endpoint at https://snowsignals.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-snowsignals-snowsignals 'https://snowsignals.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-snowsignals-snowsignals": {
      "url": "https://snowsignals.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-snowsignals-snowsignals": {
      "type": "http",
      "url": "https://snowsignals.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-snowsignals-snowsignals]
url = "https://snowsignals.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-snowsignals-snowsignals": {
      "type": "remote",
      "url": "https://snowsignals.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-snowsignals-snowsignals --url 'https://snowsignals.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-snowsignals-snowsignals:
    url: "https://snowsignals.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-snowsignals-snowsignals": {
      "Transport": "http",
      "Url": "https://snowsignals.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-snowsignals-snowsignals -t streamable-http -u 'https://snowsignals.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-snowsignals-snowsignals": {
      "type": "http",
      "url": "https://snowsignals.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1254 → 1503
- [functional] New tool “bfxpremium_get_premium”

### 2026-09-18 (score 78, −5)

- [security regression] Stability: 0.37 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “compose_phases” was removed
- [security regression] Tool “deposit_poll” was removed
- [security regression] Tool “get_balance” was removed
- [security regression] Tool “get_notifications” was removed
- [security regression] Tool “get_phase” was removed
- [security regression] Tool “get_usage” was removed
- [security regression] Tool “list_phase_meta” was removed
- [security regression] Tool “phase_resolution_stats” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] New tool “system_deposit_poll”
- [functional] New tool “system_get_balance”
- [functional] New tool “system_get_notifications”
- [functional] New tool “system_get_usage”
- [functional] New tool “trendvane_compose_phases”
- [functional] New tool “trendvane_get_phase”
- [functional] New tool “trendvane_list_phase_meta”
- [functional] New tool “trendvane_phase_resolution_stats”

### 2026-09-16 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 79, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-06 (score 78)

First indexed and scored.

## MCP tools (9)

### `trendvane_list_phase_meta` (~79 tokens)

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.

### `trendvane_phase_resolution_stats` (~95 tokens)

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.

### `system_get_notifications` (~113 tokens)

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.

Input parameters:

- `category` (string): Drill into one category.
- `cursor` (string): Opaque pagination cursor from a previous nextCursor (requires category).

### `system_get_balance` (~88 tokens)

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.

### `system_get_usage` (~101 tokens)

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.

Input parameters:

- `before` (integer): id cursor from a previous page's nextBefore (older rows).
- `limit` (integer): Rows per page (1–200, default 50).

### `system_deposit_poll` (~69 tokens)

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.

### `trendvane_get_phase` (~161 tokens)

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.

Input parameters:

- `currency` (string, required): The currency to classify. Call trendvane_list_phase_meta for the enabled set.
- `kind` (string, required): 'boundary' = the settled reading from the last closed bar; 'updates' = the live reading still forming in the current bar.
- `tf` (string): Timeframe; omit or 'all' for every enabled timeframe.

### `trendvane_compose_phases` (~120 tokens)

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.

Input parameters:

- `currencies` (array, required)
- `kind` (string, required): 'boundary' = the settled reading from the last closed bar; 'updates' = the live reading still forming in the current bar.
- `tfs` (array, required)

### `bfxpremium_get_premium` (~139 tokens)

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.

Input parameters:

- `updates` (boolean): Set true to append the rolling intra-day reading (the last closed sub-daily bucket) to the daily reading. Defaults to false.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-snowsignals-snowsignals/snowsignals#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 81
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 78

## Common questions

### What is the io.snowsignals/snowsignals MCP server?

io.snowsignals/snowsignals is an MCP server listed in the public MCP registry as io.snowsignals/snowsignals. Market-phase classifications over a metered API, phase events per currency and timeframe. This page covers its hosted endpoint (https://snowsignals.io/mcp).

### Is the io.snowsignals/snowsignals MCP server safe to use?

io.snowsignals/snowsignals scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.snowsignals/snowsignals MCP server expose?

io.snowsignals/snowsignals exposes 9 tools: trendvane_list_phase_meta, trendvane_phase_resolution_stats, system_get_notifications, system_get_balance, system_get_usage, and 4 more. Their descriptions and schemas cost roughly 965 tokens of context every time the server is loaded.

### Does the io.snowsignals/snowsignals MCP server require authentication?

Yes. io.snowsignals/snowsignals asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.snowsignals/snowsignals MCP server still maintained?

io.snowsignals/snowsignals is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://snowsignals.io/mcp
- Website: https://snowsignals.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-snowsignals-snowsignals/snowsignals.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-snowsignals-snowsignals/snowsignals.json
- HTML version of this page: https://verifymcp.io/servers/io-snowsignals-snowsignals/snowsignals