# MoveSurge (remote · movesurge.com)

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

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `movesurge.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-movesurge-movesurge/movesurge.md), [page](https://verifymcp.io/servers/com-movesurge-movesurge/movesurge)

## Channel facts

- Endpoint: `https://movesurge.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 553 tokens (~110/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the MoveSurge MCP server?

MoveSurge is a hosted endpoint at https://movesurge.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-movesurge-movesurge 'https://movesurge.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-movesurge-movesurge": {
      "url": "https://movesurge.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-movesurge-movesurge]
url = "https://movesurge.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-movesurge-movesurge": {
      "type": "remote",
      "url": "https://movesurge.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-movesurge-movesurge --url 'https://movesurge.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-movesurge-movesurge:
    url: "https://movesurge.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-movesurge-movesurge": {
      "Transport": "http",
      "Url": "https://movesurge.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-movesurge-movesurge -t streamable-http -u 'https://movesurge.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 74)

First indexed and scored.

## MCP tools (5)

### `search_headlines` (~148 tokens)

Search market 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'.

Input parameters:

- `hours` (integer): Look-back window in hours (1-336, default 24).
- `limit` (integer): Max results (1-50, default 20).
- `query` (string): Free text to match in the headline.
- `ticker` (string): Restrict to a ticker, e.g. NVDA.

Output parameters:

- `count` (integer)
- `headlines` (array)
- `window_hours` (integer)

### `top_movers` (~109 tokens)

Biggest measured 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.

Input parameters:

- `hours` (integer): Look-back window in hours (1-336, default 24).
- `limit` (integer): Max results (1-50, default 10).
- `min_move_pct` (number): Minimum absolute move percent (default 0.5).

Output parameters:

- `count` (integer)
- `min_move_pct` (number)
- `movers` (array): Ranked by the largest absolute measured move, biggest first.
- `window_hours` (integer)

### `ticker_history` (~87 tokens)

Ticker event history

Recent tape events for one ticker with each event's measured reaction. Use to answer 'what has been driving <ticker> lately'.

Input parameters:

- `days` (integer): Look-back window in days (1-60, default 7).
- `limit` (integer): Max results (1-50, default 20).
- `ticker` (string, required): Ticker symbol, e.g. WDAY.

Output parameters:

- `error` (string)
- `events` (array)
- `ticker` (string)
- `window_days` (integer)

### `get_article` (~54 tokens)

Read an explainer 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.

Input parameters:

- `slug` (string): Article slug; omit to list recent articles.

Output parameters:

- `articles` (array): Returned instead of one article when no slug is given.
- `error` (string)
- `markdown` (string)
- `slug` (string)
- `title` (string)
- `url` (string)

### `coverage_stats` (~72 tokens)

Coverage statistics

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.

Output parameters:

- `continuous_months_of_coverage` (integer)
- `coverage_note` (string)
- `distinct_tickers_last_90d` (integer)
- `earliest_event` (string|null)
- `events_last_30d` (integer)
- `events_with_measured_reaction` (integer)
- `latest_event` (string|null)
- `measured_reactions_last_30d` (integer)
- `method` (string)
- `total_events` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-movesurge-movesurge/movesurge#diagnostics

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 74

## Common questions

### What is the MoveSurge MCP server?

MoveSurge is an MCP server listed in the public MCP registry as com.movesurge/movesurge. Market news with the measured price reaction attached to the event that caused it. This page covers its hosted endpoint (https://movesurge.com/mcp).

### Is the MoveSurge MCP server safe to use?

MoveSurge scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MoveSurge MCP server expose?

MoveSurge exposes 5 tools: search_headlines, top_movers, ticker_history, get_article, coverage_stats. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.

### Does the MoveSurge MCP server require authentication?

No. We connected to MoveSurge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MoveSurge MCP server still maintained?

MoveSurge is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://movesurge.com/mcp
- Website: https://movesurge.com/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-movesurge-movesurge/movesurge.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-movesurge-movesurge/movesurge.json
- HTML version of this page: https://verifymcp.io/servers/com-movesurge-movesurge/movesurge