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.

Coil Live

REMOTE · COIL.TRADE · 2 COMPONENTS

Trading discipline for AI agents: when to trade or sit in cash, on 650+ US stocks and ETFs

+1 this week 86 Trust /100

Last scanned (14 hours ago)

Scores higher than 88% 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 Security83
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability75
  • 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
  • Context-footprint check failed: tool/resource definitions use about 9373 tokens (~183/item across 51 items; 51 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

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

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 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_stock_read” rewrote its description, which is the text the model reads security
    • Tool “get_stock_read_live” rewrote its description, which is the text the model reads security
    • Server version: 2.7.0 → 2.8.0 functional
    • New tool “get_technical_rating” functional
    • New tool “get_technical_rating_live” functional
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_full_board” rewrote its description, which is the text the model reads security
    • Tool “get_hold_state_live” rewrote its description, which is the text the model reads security
    • Tool “get_market_leaders_live” rewrote its description, which is the text the model reads security
    • Tool “get_market_regime_live” rewrote its description, which is the text the model reads security
    • Tool “get_morning_brief_live” rewrote its description, which is the text the model reads security
    • Tool “get_rotation_live” rewrote its description, which is the text the model reads security
    • Tool “get_crypto_day” rewrote its description, which is the text the model reads security
    • Tool “get_sector_read_live” rewrote its description, which is the text the model reads security
    • Tool “get_stock_read” rewrote its description, which is the text the model reads security
    • Tool “get_stock_read_live” rewrote its description, which is the text the model reads security
    • Tool “why_not_live” rewrote its description, which is the text the model reads security
    • Tool “get_buy_list_live” rewrote its description, which is the text the model reads security
    • Tool “check_my_trade_live” rewrote its description, which is the text the model reads security
    • Tool “get_crypto_day_live” rewrote its description, which is the text the model reads security
    • Tool “get_crypto_night_live” rewrote its description, which is the text the model reads security
    • Tool “get_crypto_setups_live” rewrote its description, which is the text the model reads security
    • Tool “get_day_board” rewrote its description, which is the text the model reads security
    • Tool “get_day_board_live” rewrote its description, which is the text the model reads security
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 2.6.0 → 2.7.0 functional
  • 15 Nov 26 +1
    • Stability: fail → pass ▲ security
  • 13 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 9 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_sector_read” rewrote its description, which is the text the model reads security
    • Tool “check_my_trade” rewrote its description, which is the text the model reads security
    • Tool “get_buy_list” rewrote its description, which is the text the model reads security
    • Tool “get_day_board” rewrote its description, which is the text the model reads security
    • Tool “get_hold_state” rewrote its description, which is the text the model reads security
    • Tool “get_market_leaders” rewrote its description, which is the text the model reads security
    • Tool “get_market_regime” rewrote its description, which is the text the model reads security
    • Tool “get_morning_brief” rewrote its description, which is the text the model reads security
    • Tool “get_rotation” rewrote its description, which is the text the model reads security
    • Tool “get_stock_read” rewrote its description, which is the text the model reads security
    • Tool “why_not” rewrote its description, which is the text the model reads security
    • Server version: 2.5.1 → 2.6.0 functional
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_engine_feed” rewrote its description, which is the text the model reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://coil.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=coil.trade CN=WE1,O=Google Trust Services,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA256 42a853d329920d5413acde4ca37a75b8
SANs: coil.trade, *.coil.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 secure

Validation of coil.trade. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
trade. DS published 64969 8 Verified
coil.trade. DS published 2371 13 Verified
coil.trade. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://coil.trade/mcp Verified 200
http (plaintext) http://coil.trade/mcp HTTPS enforced 301 https://coil.trade/mcp
MCP tools · 51 exposed · ~8,257 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
why_not_live ~226

Why isn't Coil buying NVDA right now, on the live board? Why a name is not a buy today, in plain words: the market gate, a chase, a falling trend, a report coming up or no entry window. The reason one stock or ETF is not a candidate, read on the live board and recomputed about every 5 minutes in market hours: the gate for its book and sector, its entry window and earnings inside five trading days, with the same answer shape as the delayed read. dip: {ok, codes, setup}: present only for oversold-pullback candidates; a dip buy only on a completed hourly turn above the entry-quality and depth floors. Live version. Coil Live is a subscription with a 7-day free trial; subscribers connect the Coil Live connector and sign in, and this read returns live data. Agents with an x402 wallet can also pay per call. Without a subscription or an x402 wallet it returns a PaymentRequired object and no data.

NameTypeReqDescription
symbolstringyesTicker, e.g. NVDA

No output schema declared.

No examples provided.

Install

How do I install the Coil Live MCP server?

Coil Live is a hosted endpoint at https://coil.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 · coil.trade

# add to Claude Code
claude mcp add --transport http trade-coil-stock-market-scanner 'https://coil.trade/mcp'
Common questions

What is the Coil Live MCP server?

Coil Live is an MCP server listed in the public MCP registry as trade.coil/stock-market-scanner. Trading discipline for AI agents: when to trade or sit in cash, on 650+ US stocks and ETFs. This page covers its hosted endpoint (https://coil.trade/mcp).

Is the Coil Live MCP server safe to use?

Coil Live scores 86 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 Coil Live MCP server expose?

Coil Live exposes 51 tools: get_market_regime, get_buy_list, get_stock_read, get_market_leaders, get_market_leaders_live, and 46 more. Their descriptions and schemas cost roughly 8,257 tokens of context every time the server is loaded.

Does the Coil Live MCP server require authentication?

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

Is the Coil Live MCP server still maintained?

Coil Live 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 Coil Live MCP server?

VerifyMCP ran 13 checks on Coil Live, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.