Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

spicytrade

REMOTE · SPICY.TRADE

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

Available components

+3 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 934 tokens (~103/item across 9 items; 8 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% 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 8 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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 753 → 934 ▼ functional
    • Schema quality: fair → good functional
    • New tool “sign_in” functional
  • 14 Nov 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.

  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 66

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://spicy.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=spicy.trade CN=WE1,O=Google Trust Services,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA256 87e29f0fd3e711c413e908e827c508f3
SANs: spicy.trade, *.spicy.trade
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 spicy.trade. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
trade. DS published 64969 8 Verified
spicy.trade. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spicy.trade/mcp Verified 200
http (plaintext) http://spicy.trade/mcp Inconclusive 405
MCP tools · 8 exposed · ~705 tokens

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 →

Tool Tokens
read_catalysts ~79

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).

NameTypeReqDescription
horizonDaysinteger–Calendar days ahead; default and maximum 180.
symbolsarrayyes–

No output schema declared.

No examples provided.

read_daily_brief ~82

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.

NameTypeReqDescription
beforestring–A market date, YYYY-MM-DD.

No output schema declared.

No examples provided.

read_instrument_quotes ~51

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.

NameTypeReqDescription
symbolsarrayyes–

No output schema declared.

No examples provided.

read_market_metrics ~61

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.

NameTypeReqDescription
symbolsarrayyesTicker symbols; a leading $ cashtag is read as the bare symbol.

No output schema declared.

No examples provided.

read_price_history ~219

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.

NameTypeReqDescription
endDatestring–Inclusive end date in YYYY-MM-DD form. Defaults to today.
intervalstring–Daily by default.
limitinteger–Most recent rows to return. Defaults to 120.
startDatestring–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.
studiesarray–Optional studies from adjusted closes; kind is SMA, EMA, RSI, BBANDS or MACD, uppercase. Defaults: period 14; MACD 12/26/9; Bollinger deviations 2.
symbolstringyes–

No output schema declared.

No examples provided.

read_watchlist ~19

Every symbol spicytrade keeps loaded, alphabetized.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_symbols ~65

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.

NameTypeReqDescription
querystringyesTicker or company-name fragment.

No output schema declared.

No examples provided.

sign_in ~129

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · spicy.trade

# add to Claude Code
claude mcp add --transport http ferdousbhai-spicytrade 'https://spicy.trade/mcp'
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.