# StockFloc Fire & Ice (remote · api.stockfloc.com)

Today's fire and ice stock movers and the Floc Heat Index, from the most visual stock watchlist.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `api.stockfloc.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api.md), [page](https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api)

## Channel facts

- Endpoint: `https://api.stockfloc.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.5`

## 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-11-06.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 405 tokens (~202/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the StockFloc Fire & Ice MCP server?

StockFloc Fire & Ice is a hosted endpoint at https://api.stockfloc.com/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 com-stockfloc-fire-and-ice 'https://api.stockfloc.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-stockfloc-fire-and-ice": {
      "url": "https://api.stockfloc.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-stockfloc-fire-and-ice": {
      "type": "http",
      "url": "https://api.stockfloc.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-stockfloc-fire-and-ice]
url = "https://api.stockfloc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-stockfloc-fire-and-ice": {
      "type": "remote",
      "url": "https://api.stockfloc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-stockfloc-fire-and-ice --url 'https://api.stockfloc.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-stockfloc-fire-and-ice:
    url: "https://api.stockfloc.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-stockfloc-fire-and-ice": {
      "Transport": "http",
      "Url": "https://api.stockfloc.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-stockfloc-fire-and-ice -t streamable-http -u 'https://api.stockfloc.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-stockfloc-fire-and-ice": {
      "type": "http",
      "url": "https://api.stockfloc.com/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-11-06 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 71, +1)

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

### 2026-11-01 (score 70, +1)

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

### 2026-10-30 (score 69, +1)

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

### 2026-10-28 (score 68, +1)

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

### 2026-10-26 (score 67, +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-10-24 (score 66, +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-10-22 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (2)

### `get_market_heat` (~122 tokens)

Get the StockFloc market heat

Today's StockFloc Floc Heat Index, a 0 to 100 daily market-breadth gauge (50 is neutral; above 50 the market ran hot, below 50 it froze), plus how many of the most-traded US stocks are on fire (up 10% or more) versus frozen (down 10% or more). Use this when someone asks how hot or cold the stock market is today, or how many stocks made big moves. US stocks only, delayed about 15 minutes; returns the index and counts, not prices.

### `get_hot_stocks` (~141 tokens)

Get today's fire and ice stocks

Today's biggest US stock movers in StockFloc terms: stocks on fire (the largest gainers) and frozen (the largest losers), each with its percent change for the day. Use this when someone asks which stocks are on fire, frozen, or moving the most today. Returns up to 10 ticker symbols per side with percent change only: no prices and no quote for a specific ticker. Delayed about 15 minutes.

Input parameters:

- `limit` (integer): How many per side (1 to 10). Default 5.
- `side` (string): fire = top gainers, ice = top losers, both = both lists. Default both.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api#diagnostics

## Score history

- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65
- 2026-10-22: 65
- 2026-10-21: 64

## Common questions

### What is the StockFloc Fire & Ice MCP server?

StockFloc Fire & Ice is an MCP server listed in the public MCP registry as com.stockfloc/fire-and-ice. Today's fire and ice stock movers and the Floc Heat Index, from the most visual stock watchlist. This page covers its hosted endpoint (https://api.stockfloc.com/mcp).

### Is the StockFloc Fire & Ice MCP server safe to use?

StockFloc Fire & Ice scores 72 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 StockFloc Fire & Ice MCP server expose?

StockFloc Fire & Ice exposes 2 tools: get_market_heat, get_hot_stocks. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.

### Does the StockFloc Fire & Ice MCP server require authentication?

No. We connected to StockFloc Fire & Ice without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the StockFloc Fire & Ice MCP server still maintained?

StockFloc Fire & Ice is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the StockFloc Fire & Ice MCP server?

VerifyMCP ran 12 checks on StockFloc Fire & Ice, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about StockFloc Fire & Ice: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.stockfloc.com/mcp
- Website: https://stockfloc.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api.json
- HTML version of this page: https://verifymcp.io/servers/com-stockfloc-fire-and-ice/api