Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
MoveSurge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Market news with the measured price reaction attached to the event that caused it.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http movesurge-mcp https://movesurge.com/mcp
# 2 — ask your agent for something these tools do
# search_headlines, top_movers, ticker_history and 6 more
MoveSurge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MOAll 1 server
movesurge1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http movesurge-mcp https://movesurge.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the MoveSurge market-news tape and return matching headlines with the measured price reaction attached to each. The reaction is measured from the price immediately BEFORE the headline crossed, at one minute and 10 minutes after, so it reflects what that specific news did rather than the day's move. Use for questions like 'what moved on chip supply news today'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text to match in the headline. |
| ticker | string | no | Restrict to a ticker, e.g. NVDA. |
| hours | integer | no | Look-back window in hours (1-336, default 24). |
| before_hours | integer | no | End the window this many hours ago; use with hours to inspect earlier parts of the day. |
| impact | string | no | Optional existing event-impact classification. |
| limit | integer | no | Max results (1-50, default 20). |
The events with the largest MEASURED price reactions in a window, ranked by the size of the move attributed to the event. Answers 'what actually moved and why'. Only returns events where a reaction was successfully measured.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | Look-back window in hours (1-336, default 24). |
| min_move_pct | number | no | Minimum absolute move percent (default 0.5). |
| limit | integer | no | Max results (1-50, default 10). |
Recent tape events for one ticker with each event's measured reaction. Use to answer 'what has been driving <ticker> lately'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. WDAY. |
| days | integer | no | Look-back window in days (1-60, default 7). |
| limit | integer | no | Max results (1-50, default 20). |
Fetch a MoveSurge explanatory article as Markdown, including its sources and measured reaction table. Call with no slug to list the 25 most recent articles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Article slug; omit to list recent articles. |
Auditable statistics about what MoveSurge covers and how it measures: date range, total events, how many carry a measured price reaction, distinct tickers, and unbroken months of coverage. Use to judge whether this source is worth citing, or to state its coverage accurately. Figures are computed live, not asserted.
No parameter schema on file.
Abnormal price moves that MoveSurge detected first and then investigated, each with the cause it found, the evidence, a confidence level and how the move followed through. Use for 'why did oil / the Nasdaq / a stock suddenly move' when no single headline explains it. Only moves whose cause was established with medium or high confidence are published.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Restrict to one instrument symbol, e.g. WTI or NQ. |
| hours | integer | no | Look-back window in hours (1-336, default 72). |
| limit | integer | no | Max results (1-50, default 10). |
Reported earnings with EPS and revenue against the consensus estimate, the beat/miss outcome, guidance direction and, where measured, the price reaction to the release; plus who reports next. Use for 'did NVDA beat', 'how did the stock react to earnings' or 'who reports this week'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | no | Restrict to one ticker, e.g. NKE. |
| hours | integer | no | Results look-back in hours (1-336, default 72). |
| days_ahead | integer | no | Upcoming reports window in days (0-14, default 7; 0 skips it). |
| limit | integer | no | Max rows per list (1-50, default 20). |
Released economic data (CPI, payrolls, PMIs, central-bank decisions and more) with actual vs forecast vs previous, the surprise direction and the measured market reaction in the minutes after the release; plus the scheduled releases ahead. Defaults to high-impact releases. Use for 'what did CPI come in at and how did markets react' or 'what data is out this week'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | Two-letter country code, e.g. US, GB, EU, JP. |
| impact | string | no | high (default) or all. |
| hours | integer | no | Released-data look-back in hours (1-336, default 48). |
| days_ahead | integer | no | Upcoming window in days (0-14, default 3; 0 skips it). |
| limit | integer | no | Max rows per list (1-50, default 20). |
Recent Truth Social posts by President Trump as they crossed the tape, with the measured market reaction where the post moved an instrument. Use for 'what has Trump posted today' or 'did his tariff post move markets'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text to match in the post, e.g. tariff. |
| hours | integer | no | Look-back window in hours (1-336, default 24). |
| with_reaction_only | boolean | no | Only posts with a measured market reaction. |
| limit | integer | no | Max results (1-50, default 20). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MoveSurge or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish MoveSurge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.