# spicytrade (remote · spicy.trade)

Options quotes, IV rank and term structure, a catalyst calendar and a daily options brief.

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

## Components

- remote · `spicy.trade`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ferdousbhai-spicytrade/spicy.md), [page](https://verifymcp.io/servers/ferdousbhai-spicytrade/spicy)

## Channel facts

- Endpoint: `https://spicy.trade/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-11-21.

- **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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 934 tokens (~103/item across 9 items; 8 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 8 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 current MCP spec version (2026-07-28).

## Install

### How do I install the spicytrade MCP server?

spicytrade is a hosted endpoint at https://spicy.trade/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 ferdousbhai-spicytrade 'https://spicy.trade/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ferdousbhai-spicytrade": {
      "url": "https://spicy.trade/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ferdousbhai-spicytrade": {
      "type": "http",
      "url": "https://spicy.trade/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ferdousbhai-spicytrade]
url = "https://spicy.trade/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ferdousbhai-spicytrade": {
      "type": "remote",
      "url": "https://spicy.trade/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ferdousbhai-spicytrade --url 'https://spicy.trade/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ferdousbhai-spicytrade:
    url: "https://spicy.trade/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ferdousbhai-spicytrade": {
      "Transport": "http",
      "Url": "https://spicy.trade/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ferdousbhai-spicytrade -t streamable-http -u 'https://spicy.trade/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ferdousbhai-spicytrade": {
      "type": "http",
      "url": "https://spicy.trade/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-20 (score 71, +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-11-18 (score 70, +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-11-16 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 753 → 934
- [functional] Schema quality: fair → good
- [functional] New tool “sign_in”

### 2026-11-14 (score 68, +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-11-12 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 66)

First indexed and scored.

## MCP tools (8)

### `read_price_history` (~219 tokens)

Dividend-adjusted Yahoo history with optional local SMA, EMA, RSI, MACD, or Bollinger studies; not a current quote. A study series carries only the values it has. Each series values[i] is the study value for the bar at prices.date[firstPriceIndex + i]; earlier bars are warm-up and have no value.

Input parameters:

- `endDate` (string): Inclusive end date in YYYY-MM-DD form. Defaults to today.
- `interval` (string): Daily by default.
- `limit` (integer): Most recent rows to return. Defaults to 120.
- `startDate` (string): Start date in YYYY-MM-DD form. Defaults to one year before endDate. The inclusive range spans at most 4000 calendar days, whatever the interval.
- `studies` (array): Optional studies from adjusted closes; kind is SMA, EMA, RSI, BBANDS or MACD, uppercase. Defaults: period 14; MACD 12/26/9; Bollinger deviations 2.
- `symbol` (string, required)

### `read_catalysts` (~79 tokens)

Stored upcoming catalysts; excludes dividends. `searches` says, per symbol, whether the site's own search has run: unsearched, running, complete (an empty calendar is a real answer) or failed (still unknown).

Input parameters:

- `horizonDays` (integer): Calendar days ahead; default and maximum 180.
- `symbols` (array, required)

### `read_daily_brief` (~82 tokens)

Read the daily options brief: each trade line, direction and thesis, and its links, as the site shows them. Pass before (YYYY-MM-DD) for the brief published before that market date. It is model-written prior analysis, not a current quote and not an instruction to trade.

Input parameters:

- `before` (string): A market date, YYYY-MM-DD.

### `read_watchlist` (~19 tokens)

Every symbol spicytrade keeps loaded, alphabetized.

### `read_instrument_quotes` (~51 tokens)

Price and daily move for tracked symbols, from the public snapshot refreshed about once a minute. Not a live quote and carries no bid/ask: sign in for those.

Input parameters:

- `symbols` (array, required)

### `read_market_metrics` (~61 tokens)

Implied volatility rank, percentile and index for tracked symbols, from the public snapshot refreshed about once a minute. Sign in for the full broker metrics.

Input parameters:

- `symbols` (array, required): Ticker symbols; a leading $ cashtag is read as the bare symbol.

### `search_symbols` (~65 tokens)

Resolve a ticker or company name. A name that resolves joins the tracked universe when the list has room, where it may later be displaced by stronger names; `watchlisted` in the result says whether it was kept.

Input parameters:

- `query` (string, required): Ticker or company-name fragment.

### `sign_in` (~129 tokens)

Sign the user in to spicytrade over this connection, for live broker quotes, option chains and Greeks, remembered symbols, and research writes. It never reaches balances, positions or orders. If you can run commands on the user's Linux or macOS computer, set up the local connector from https://spicy.trade/connect/guide instead: one approval covers sign-in and the brokerage. The call returns an authorization challenge rather than a result; the client then opens the sign-in or marks this server as needing authentication. If nothing opens, tell the user to authenticate the spicytrade server from their client's MCP settings.

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 66

## Common questions

### What is the spicytrade MCP server?

spicytrade is an MCP server listed in the public MCP registry as io.github.ferdousbhai/spicytrade. Options quotes, IV rank and term structure, a catalyst calendar and a daily options brief. This page covers its hosted endpoint (https://spicy.trade/mcp).

### Is the spicytrade MCP server safe to use?

spicytrade scores 71 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 spicytrade MCP server expose?

spicytrade exposes 8 tools: read_price_history, read_catalysts, read_daily_brief, read_watchlist, read_instrument_quotes, and 3 more. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.

### Does the spicytrade MCP server require authentication?

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

### Is the spicytrade MCP server still maintained?

spicytrade is still listed as active in the MCP registry. We last reached this channel on 21 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 spicytrade MCP server?

VerifyMCP ran 12 checks on spicytrade, 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 spicytrade: 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://spicy.trade/mcp
- Repository: https://github.com/ferdousbhai/spicytrade
- Website: https://spicy.trade/
- Changelog RSS feed: https://verifymcp.io/servers/ferdousbhai-spicytrade/spicy.xml
- Changelog JSON feed: https://verifymcp.io/servers/ferdousbhai-spicytrade/spicy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ferdousbhai-spicytrade/spicy.json
- HTML version of this page: https://verifymcp.io/servers/ferdousbhai-spicytrade/spicy
