TradeMCP News Docs

Why is it moving?

Unusual price moves and the story or scheduled release that most likely explains them.

The service watches 1-minute prices for the tracked assets. A 15-minute move of at least 2.5 times the asset's hourly volatility is recorded as a move, then matched against stories and scheduled releases that appeared shortly before it. Needs sentiment:read.

The cause is a likely cause based on timing, not proof. no_news means no matching story was found. Not financial advice.

MethodPath
GET/v1/movesRecent moves, newest first. cause (news, scheduled, no_news), since/until (default last 24 hours), limit up to 100, cursor
GET/v1/assets/{symbol}/movesMoves of one asset
GET/v1/assets/{symbol}/contextSentiment trend, open flags, recent moves, upcoming releases and top stories in one call

Each move has start, end, move_pct, z, cause, and likely_causes[] ranked by fit (headline, link, event type, minutes before the move). Scheduled releases that fit are listed in scheduled. A move first labelled no_news is checked again once after 30 minutes, because stories can be published after the price reacts, so its cause can change.

Flags

Open flags appear in the asset context. They mark bullish_news_falling_price and bearish_news_rising_price (news tone and price disagree) and coverage_extreme (unusually many stories). They are shown in the asset context and in Telegram, and are an observation, not a signal.

Price source: Yahoo Finance by default, with history limited to about 30 days and occasional missing minutes on FX pairs.

On this page