io.snowsignals/snowsignals
REMOTE · SNOWSIGNALS.IO · SCANNED SEP 24
Market-phase classifications over a metered API — phase events per currency and timeframe.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 18 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 9 additions. See how to fix → Fail
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · snowsignals.io
claude mcp add --transport http io-snowsignals-snowsignals 'https://snowsignals.io/mcp'
{
"mcpServers": {
"io-snowsignals-snowsignals": {
"url": "https://snowsignals.io/mcp"
}
}
} {
"servers": {
"io-snowsignals-snowsignals": {
"type": "http",
"url": "https://snowsignals.io/mcp"
}
}
} [mcp_servers.io-snowsignals-snowsignals] url = "https://snowsignals.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-snowsignals-snowsignals": {
"type": "remote",
"url": "https://snowsignals.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-snowsignals-snowsignals --url 'https://snowsignals.io/mcp' --transport streamable-http
mcp_servers:
io-snowsignals-snowsignals:
url: "https://snowsignals.io/mcp" {
"McpServers": {
"io-snowsignals-snowsignals": {
"Transport": "http",
"Url": "https://snowsignals.io/mcp"
}
}
} assistant mcp add io-snowsignals-snowsignals -t streamable-http -u 'https://snowsignals.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1254 → 1503 ▼ functional
- New tool “bfxpremium_get_premium” functional
- 18 Sept 26 −5
- Stability: 0.37 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “compose_phases” was removed ▼ security
- Tool “deposit_poll” was removed ▼ security
- Tool “get_balance” was removed ▼ security
- Tool “get_notifications” was removed ▼ security
- Tool “get_phase” was removed ▼ security
- Tool “get_usage” was removed ▼ security
- Tool “list_phase_meta” was removed ▼ security
- Tool “phase_resolution_stats” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- 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” functional
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 6 Sept 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://snowsignals.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=snowsignals.io | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 141bee214f08b89f0e254636d53992d8 |
| SANs: snowsignals.io, pay.snowsignals.io, *.pay.snowsignals.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of snowsignals.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| snowsignals.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://snowsignals.io/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://snowsignals.io/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://challenges.cloudflare.com 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https:; connect-src 'self' blob: https://toncenter.com https://*.toncenter.com https://*.tonapi.io https://config.ton.org https://bridge.tonapi.io wss://bridge.tonapi.io https://raw.githubusercontent.com https://solana-rpc.publicnode.com https://*.publicnode.com https://*.solana.com https://*.walletconnect.com wss://*.walletconnect.com https://*.walletconnect.org wss://*.walletconnect.org https://*.statuspage.io; frame-src 'self' https://challenges.cloudflare.com https://verify.walletconnect.com https://verify.walletconnect.org; worker-src 'self' blob:; manifest-src 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Protected resource metadata
| Document | https://snowsignals.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://snowsignals.io/mcp |
| Authorisation server | https://snowsignals.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://snowsignals.io/mcp | Verified | 200 | |
| http (plaintext) | http://snowsignals.io/mcp | HTTPS enforced | 301 | https://snowsignals.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bfxpremium_get_premium ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| updates | boolean | – | Set true to append the rolling intra-day reading (the last closed sub-daily bucket) to the daily reading. Defaults to false. |
No output schema declared.
No examples provided.
system_deposit_poll ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
system_get_balance ~88
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
system_get_notifications ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Drill into one category. |
| cursor | string | – | Opaque pagination cursor from a previous nextCursor (requires category). |
No output schema declared.
No examples provided.
system_get_usage ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | integer | – | id cursor from a previous page's nextBefore (older rows). |
| limit | integer | – | Rows per page (1–200, default 50). |
No output schema declared.
No examples provided.
trendvane_compose_phases ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currencies | array | yes | – |
| kind | string | yes | 'boundary' = the settled reading from the last closed bar; 'updates' = the live reading still forming in the current bar. |
| tfs | array | yes | – |
No output schema declared.
No examples provided.
trendvane_get_phase ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | The currency to classify. Call trendvane_list_phase_meta for the enabled set. |
| kind | string | yes | '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. |
No output schema declared.
No examples provided.
trendvane_list_phase_meta ~79
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trendvane_phase_resolution_stats ~95
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.