# MoveSurge

> Market news with the measured price reaction attached to the event that caused it.

- name: com.movesurge/movesurge
- version: 1.0.0
- connection class: unknown (unknown)
- trust: 53/100 flags: no-repository, unreachable
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.movesurge%2Fmovesurge
- tools: https://api.protogrid.dev/v1/servers/com.movesurge%2Fmovesurge/tools

**Not classified yet.** The remote endpoints have not been probed successfully, or the listing has nothing to connect to.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "movesurge": {
      "type": "http",
      "url": "https://movesurge.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 0
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website -unreachable(4 failures) +updated-27d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 9 of 9 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_article (idempotentHint); coverage_stats (idempotentHint); explained_moves (idempotentHint); …
- pass `tools.token_cost`: about 1,583 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 4 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 1,583 tokens to load them all
- tool set hash: 38479ad44d842963a6431ca57bb6f5f8
- tools last changed: 2026-10-03T08:53:13.896Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.movesurge/movesurge.svg)](https://protogrid.dev/servers/com.movesurge/movesurge)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-03 `truth_social_posts` added
  - 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'.
- 2026-10-03 `economic_data` added
  - 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'.
- 2026-10-03 `earnings` added
  - 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'.
- 2026-10-03 `explained_moves` added
  - 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.

Full history: https://api.protogrid.dev/v1/servers/com.movesurge%2Fmovesurge/changes

## Remotes

- https://movesurge.com/mcp (streamable-http, auth none, reachable false, uptime30d 0.9310345)

## Packages

_none_

## Tools (9)

- `coverage_stats`: 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.
- `earnings`: 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'.
- `economic_data`: 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'.
- `explained_moves`: 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.
- `get_article`: 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.
- `search_headlines`: 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'.
- `ticker_history`: Recent tape events for one ticker with each event's measured reaction. Use to answer 'what has been driving <ticker> lately'.
- `top_movers`: 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.
- `truth_social_posts`: 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'.