MoveSurge
com.movesurge/movesurge · 1.0.0
Market news with the measured price reaction attached to the event that caused it.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://movesurge.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 9 tools.
- Protocol
- 2025-06-18
- Calls itself
- movesurge 1.0.0
- Handshake time
- 565 ms
- HTTP status
- 200
The tools it lists (9, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_headlinesSearch 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'.
top_moversThe 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.
ticker_historyRecent tape events for one ticker with each event's measured reaction. Use to answer 'what has been driving <ticker> lately'.
get_articleFetch a MoveSurge explanatory article as Markdown, including its sources and measured reaction table. Call with no slug to list the 25 most recent articles.
coverage_statsAuditable 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.
explained_movesAbnormal 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.movesurge/movesurge, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 14 days ago. The registry entry · movesurge.com