A live trading strategy your own AI agent can follow.
Point your AI agent at Coil's MCP and it gets the board and rulebook the engine starts from
— structural stops, targets, conviction, lanes — refreshed about every 5 minutes while the market is open, plus the served trading discipline to run against it. Nothing to download, nothing to configure, no market-data account to create.
- 7 days free, then $49/mo · or $419/yr
- Renews until you cancel · access to period end
- Nothing to install · one header
- Re-scored about every 5 min in market hours
- Your agent places · we never hold your broker
FROM THE TRADING DESK
Most of our trades come from two setups on a board we score every morning. Each morning’s board is hashed into a public log, so it can’t be quietly rewritten after the fact.
The first setup is the leading names in the leading groups, bought on strength. The second is oversold stocks, bought when a completed hourly bar turns up off a low.
We buy bases and pullbacks, not stocks already extended on the day. When a losing entry broke that rule, our end-of-day post-mortem names it.
Every position has its exit named before it is bought: the place where the idea is wrong. When that level breaks, we sell, and we don’t negotiate with it.
A stop can’t sell above a gap. So starting Monday, November 2, a stock in a steep slide needs a named structure on its chart before we will touch it.
We don’t short sell or trade crypto. On down days we may buy an inverse ETF, as a hedge or as a same-day trade.
We post every exit on /results the day it closes, the red ones beside the green.
Coil trading desk
THREE TRADES FROM ONE WEEK
One trade of each exit kind (a target, a trailing stop and a stop) from the trades that closed in the week of October 26. The other round trips are on /results, newest first.
-
LRCXtargetIn Oct 27 · out Oct 29 · 2 days+6.67%SPY −0.04% · +6.71pp vs SPY
- Why we bought
- LRCX gapped down hard the morning after its October 21 earnings report. It then stopped going down: two flat closes at the post-gap level, then a higher close on the 26th. The daily chart was deeply oversold. On the 27th the hourly chart turned up off that base, and we bought it. The tape was choppy, a pre-Fed drift with a weak weekly trend. The money that was moving went into semis and software.
- Where the risk sat
- Under the post-earnings low. If that low broke, the base was not a base.
- Why we sold
- It ran into its target in two sessions. We took the pop at the open on the 29th.
-
ARWRtrailing stopIn Oct 19 · out Oct 26 · 7 days+3.41%SPY −0.14% · +3.55pp vs SPY
- Why we bought
- ARWR had made lower highs from its September 22 peak and closed at the low of the move on October 16. It was deeply oversold on the daily chart. On the 19th the hourly chart turned up, and we bought the dip.
- Where the risk sat
- Well under the October 16 low.
- Why we sold
- It bounced for two sessions and then stalled. When it gave back part of the bounce, the trailing stop sold it with the gain.
-
XLEstopIn Oct 26 · out Oct 27 · 1 day−1.78%SPY +0.56% · −2.34pp vs SPY
- Why we bought
- Energy was one of the two groups with money flowing in that morning, alongside semis. XLE had climbed for four weeks to new highs for the move, with broad participation inside the sector. We bought the leader on strength.
- Where the risk sat
- Just under Monday’s low.
- Why we sold
- Tuesday morning it broke Monday’s low, and we were out. The idea was wrong within a day, and it cost less than either winner made. That is the trade working.
FRI OCT 30 · ALL SIX RED
Six round trips closed on Friday, and all six were red. The two that hurt were dip buys in stocks that were still falling: CIFR closed −12.53% and AXSM −8.43%.
CIFR is the lesson. We bought it on October 27 as an oversold dip, on a day it was already up sharply, so it was a falling knife and a chase in the same entry. On the 30th it gapped down through its stop at the open, and a stop can’t sell above the open. No stop prevents a gap; only not owning the knife does.
What changed, live from Monday, November 2: a stock in a steep decline is no longer bought by a rule alone. We have to name a structure on its chart, such as a level that held, a higher low or a reclaim, or we pass. The record will show whether it helps.
WHAT A SKEPTICAL TRADER ASKS
- “You’re behind SPY.”
- We are, and the page says so first, at the same size as anything good. You’re buying a feed whose every call is graded in public, not a promise of returns.
- “Anyone can show three winners.”
- We showed two winners and a loser, one of each exit kind from one week. Every other round trip is on /results, newest first, green and red. Pick your own three.
- “How do I know you didn’t rewrite the calls after the fact?”
- Every morning’s board is SHA-256 hashed into an append-only public log, and a correction is appended, never rewritten. On /results your browser can check the free sample day; any other day’s names are a paid read you can hash yourself.
- Try it with no key
get_live_setupanswers keyless: product, price, header form, cadence. Call it now. - Cancel anytimeFrom your Gumroad library, no email needed; access runs to period end. No prorated refunds on partial periods. Refund policy
- Key arrives instantlyCard, PayPal or Apple Pay via Gumroad, the merchant of record. Your license key is in your receipt.
- Written to fail closedIf the feed ever stops, the rulebook tells your agent to open nothing new and keep managing exits from its own records.
Coil Live is the step past reading a board yourself.The scanner stays on our side — the same one that publishes the live, benchmarked record — and your agent calls it like any other tool. One subscription, one header, and every live tool in our MCP answers, including two things sold nowhere else: the engine feed and the served discipline.
What your agent gets, every call
Illustrative rows, not today's feed: each name carries its structural stop and target with their basis, risk-reward, buy score, conviction, entry lane and any leveraged vehicle; the served candidates[] list is what the discipline would act on right now, and an empty list is the discipline working.
- get_engine_feed — everything in the full board plus the scanner's per-name plan fields: structural stop and target with their basis, risk-reward, buy score, conviction, entry lane, leveraged vehicle, ladder placement. These fields are never sold per-call and never appear on any public surface.
- get_live_rules — the served discipline, versioned: cycle order, exits-first, stop derivation with a hard cap on how far below its entry a stop may sit, the entry guards, the day-lane rhythm, sizing that shrinks during a losing run, fail-closed rules. When the rules improve, your agent gets the update on its next read — nothing to re-download, ever.
- Every
*_livetool without per-call payment — regime, buy list, single-name reads, sectors, leaders, day board, crypto reads: the whole live catalog, flat rate, at whatever cadence you like (every 5–10 minutes in market hours is a sensible cadence; 60 calls/min headroom per license). - The human surfaces too — the same key opens the Coil Scanner board and dashboard in your browser, so you can watch what your agent is reading. The $49 tier is a strict superset of the $19 one.
- Unfiltered feed ~1.35MB — never read it into a model’s context; poll by symbols with
compact(~12KB for two names) - 60 calls/min headroom per license
- freshness.is_stale + next_refresh_at in every feed payload
- Same key opens the Scanner board in your browser
The rulebook opens on one line: small losses, big wins. Name the stop before the buy and size the position on it; cut a loser at its stop, never past a hard cap below the entry; buy pullbacks, not extensions; trade smaller when you are losing; and treat cash as a position, because a cycle with no entry is the discipline working. Version 1.6.0 wrote the three rules behind that line into the rulebook: one capped stop that sizing, the first target and the exit all use, an entry guard that skips a name extended well above the session low, and half-size entries after a run of losing closes, until one winner. Version 1.7.0 made the rulebook match the live engine's max loss, sizing, hedge and dip rules. Your agent reads the changelog and finishes open positions under the version they opened under.
Who does what
The division of labor is the product.Coil scores and serves; your agent decides and places; you own the account and the off switch.
Subscribe and connect
Renews monthly until you cancel. The engine feed, the served discipline, every live tool, and the Scanner board in your browser.
Try Coil Live free for 7 days, then $49/moJust want to try it free? Connect Coil to your agent →
Renews yearly until you cancel — twelve months for the price of about eight and a half. Pick the yearly plan at checkout.
Go yearly — $419/yr- SubscribeCard checkout via Gumroad, the merchant of record; your license key arrives instantly. Prefer a full order page? /buy/live.
- Hand your agent the keyMCP: add
https://mcp.coil.trade/mcpas a server with headerX-License-Key: your-key. Plain HTTPS:GET https://coil.trade/api/live/feedwith the same header. Either way, tell your agent: “call get_live_setup and follow it.” - Let it run dry firstThe served discipline tells every agent to start in dry-run — printing intended orders, placing nothing — until you explicitly arm it. Coil can’t enforce that on your machine and doesn’t pretend to; it is rule one of the rulebook your agent reads, and the arm switch is yours.
The whole connection, verbatim. It is the same shape as the Robinhood command, pointed at Coil's server:
claude mcp add --transport http coil https://mcp.coil.trade/mcp \
--header "X-License-Key: YOUR_GUMROAD_LICENSE_KEY"
In Claude, you can skip the header: sign in instead (Use Coil Live in Claude).
Simulated: after one add command, get_live_setup returns product, price and header form; get_live_rules returns the versioned rulebook whose first rule is dry-run; get_engine_feed returns the scored board with its candidates list and freshness flags.
Use Coil Live in Claude
Coil is in the Claude directory. Its free tools work with no sign-in; Coil Live’s live reads ask you to sign in the first time.
- Start Coil Live. Start the 7-day free trial and keep the license key from your Gumroad receipt. The trial key works.
- Add Coil from the Claude directory. In Claude, open Customize → Connectors and add Coil from the directory, or add Coil to Claude from here.
- Ask for a live read. For example, “What’s on Coil’s live buy list?” Claude shows Connect.
- Sign in. A Coil sign-in page opens. Paste your Coil Live license key from your Gumroad receipt and click Sign in.
- Allow the tools. The first time Claude uses a Coil Live tool in a chat, it asks your permission. Allow it.
Or add Coil Live as its own connector
In Claude, open Customize → Connectors, then “+ Add” → “Add custom connector”. Name it Coil Live, paste the URL https://mcp.coil.trade/live/mcp, then click Continue. Under Authentication, choose Sign in now. Under OAuth client, choose Register automatically. Claude usually selects both for Coil, but check them. Click Continue, then Add. Then click Connect and sign in with your Coil Live license key, as in step 4.
Only a Coil Live license key signs in (a Coil Scanner key does not). Coil never sees your brokerage account. On a Team or Enterprise plan, an Owner adds custom connectors.
Claude Desktop, Cursor and Windsurf launch servers by command, and their connector screens cannot send a custom header, so use the npm bridge with the key in its environment (claude_desktop_config.json or your client’s MCP settings):
{ "mcpServers": { "coil": { "command": "npx", "args": ["-y", "coil-mcp"],
"env": { "COIL_LICENSE_KEY": "YOUR_GUMROAD_LICENSE_KEY" } } } }
Any other MCP client that speaks streamable HTTP: server URL https://mcp.coil.trade/mcp and the request header X-License-Key: YOUR_GUMROAD_LICENSE_KEY, set wherever that client keeps custom headers.
Three tools to know. get_live_setup returns the product, price, cadence and the exact header form — call it first, it needs no key:
curl -s https://mcp.coil.trade/mcp -H "content-type: application/json" -H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_live_setup","arguments":{}}}'
get_engine_feed returns the board the engine starts from: per-name structural stop and target, conviction, entry lane, the vehicle attached when a setup earns one, and a served candidates[] list — an empty list means the discipline is working, not an outage, and the payload says so. get_live_rules returns the versioned rulebook with its changelog. Every feed payload carries field_notes, timestamps_note and freshness.is_stale, so your agent never guesses at vocabulary or does clock math. The rest of the live catalog opens on the same key. Checked against the live server 2026-09-01.
What you are buying is the discipline, not the returns
The record on our results page is one real account — ours — running these rules with real money, published every session including the losing ones.It is evidence that the discipline works when it is followed. It is not a result your agent inherits, and we would rather tell you that here than have you find out in month two.
Your agent reads the feed and the rulebook the engine starts from, and it will still trade differently than ours does. Every one of these pulls the two apart:
Illustrative: identical signals still print different numbers once your fills, your equity and your clock are applied; what transfers is the discipline, not the profit and loss.
So read the record for what it actually proves: that the capped stop, the entry guards, the sizing precedence and the exits-first cycle add up to something that has been run on a real account and shown its work every session, up and down. That discipline is the product. The feed is how your agent receives it, kept current. The number at the end of your own year is yours.
Which Coil is right for you
Coil Scanner is the board in a browser tab, for the trader who places their own orders. Coil Live serves your agent our board — the one the engine starts from — with stops, targets, lanes and the served discipline. The question is who places the orders.
Common questions
Will my agent's results match the live record?
No — and that gap is not small print. Your agent polls at different moments than ours, so it sees a different candidate list; the engine's final ranking adds an internal macro and fundamental check that the feed does not carry; it sizes every position against your equity, not ours; and it fills at your broker, across your spread, under your own settled-cash and pattern-day-trader limits. What transfers between the two accounts is the discipline, not the profit and loss. Everything that makes them diverge →
Does Coil see my brokerage account or place my orders?
Never. Coil serves data and rules over MCP and HTTP; your agent runs on your machine, holds your broker connection, and places every order itself. We have no way to see your account, your keys, your balances or your orders. One honest footnote: if your agent filters the feed by symbol — the recommended way to keep calls small — those symbols reach our server as part of the request, tied to your license, like any API parameter. We ask for nothing else.
What will polling cost me?
The subscription is flat. Your agent's own token bill is yours, and the feed is the biggest lever on it: measured on the live board, an unfiltered read is about 1.35MB (hundreds of thousands of tokens) and a plain two-name symbols read is about 70KB. So the setup tool tells your agent never to read the unfiltered feed into its context, and to poll with a symbols filter (your open positions plus the served candidates) and compact=true, which brings a two-name read to about 12KB. Optional fields picks engine fields, and limit with cursor pages the whole board by symbol. At the recommended cadence that is a call every 5–10 minutes in market hours, a few KB each.
What happens if I cancel?
The feed stops at period end, and the served discipline is written to fail closed: it tells an agent that loses the feed to stop opening new positions and keep managing its exits from its own local records. Cancelling never strands you mid-trade blind.
Is there a trial?
Yes: 7 days free. Your card is taken at checkout and charged when the 7 days end, unless you cancel first from your Gumroad library. Before you start, get_live_setup answers with no key, the free preview shows a delayed slice of the same board, and the record is public down to the session.
Which AI agents work with Coil Live?
Any strong coding agent that can call an MCP server or plain HTTPS and run on a schedule — Claude Code is what we run ourselves, but nothing here is Claude-only. Your agent sends the license key as a header; that is the whole integration.
The fine print, plainly
- Impersonal by design. Every subscriber sees identical numbers. Nothing here is individualized investment advice; markets can lose money, and the discipline bounds losses rather than preventing them.
- Renews until you cancel. Monthly or yearly, billed by Gumroad; cancel from your library and access runs to period end. No prorated refunds on partial periods; billing errors are always corrected. The policy in full.
- What reaches our server. Your license key and whatever your agent asks for, including the symbols it filters by. Never your broker connection, keys, balances or orders.
- The rules can change. Improvements are served on your agent's next read, versioned and logged in the changelog it can read; if you want your agent to hold a version, tell it to.
Coil Live
The board and rulebook the engine starts from, served to your agent — plus the discipline to run it. The easiest setup we sell.
Try Coil Live free for 7 days, then $49/moCancel anytime from your Gumroad library; access runs to period end. An impersonal research publication — not investment advice.