# Tremor Watch (remote · api.antevo.ch)

How many market relationships stopped behaving this week: the Antevo Tremor Index, since 1997.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.antevo.ch`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp.md), [page](https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp)

## Channel facts

- Endpoint: `https://api.antevo.ch/mcp/tremor/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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 940 tokens (~235/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Tremor Watch MCP server?

Tremor Watch is a hosted endpoint at https://api.antevo.ch/mcp/tremor/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 ch-antevo-tremor-watch 'https://api.antevo.ch/mcp/tremor/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ch-antevo-tremor-watch": {
      "url": "https://api.antevo.ch/mcp/tremor/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ch-antevo-tremor-watch": {
      "type": "http",
      "url": "https://api.antevo.ch/mcp/tremor/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ch-antevo-tremor-watch]
url = "https://api.antevo.ch/mcp/tremor/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ch-antevo-tremor-watch": {
      "type": "remote",
      "url": "https://api.antevo.ch/mcp/tremor/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ch-antevo-tremor-watch --url 'https://api.antevo.ch/mcp/tremor/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ch-antevo-tremor-watch:
    url: "https://api.antevo.ch/mcp/tremor/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ch-antevo-tremor-watch": {
      "Transport": "http",
      "Url": "https://api.antevo.ch/mcp/tremor/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ch-antevo-tremor-watch -t streamable-http -u 'https://api.antevo.ch/mcp/tremor/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ch-antevo-tremor-watch": {
      "type": "http",
      "url": "https://api.antevo.ch/mcp/tremor/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-11-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 66)

First indexed and scored.

## MCP tools (4)

### `get_tremor_index` (~173 tokens)

Get tremor index

This week's Antevo Tremor Index, for the week that ended on Friday: the share of market pairs breaking (correlation two standard deviations from its own previous two years), how many times a normal Friday that is (the median week since 2001), its status (Calm, Elevated, High or Severe: the 75th, 90th and 97th percentiles since 2001), its rank among every Friday since 2001, and the split into links strengthening (moving closer) and weakening (coming apart). With it: each of the seven families against its own normal Friday, last week, the worst week on record, the value as first published, and as context realized volatility as a multiple of its normal (1.0) with its percentile since 2001.

### `get_tremor_history` (~181 tokens)

Get tremor history

The Antevo Tremor Index over time, oldest first: each reading's week, level, how many times a normal Friday it was, its status (Calm, Elevated, High or Severe) and the split into strengthening and weakening, with the peak of the period. weeks is how many Fridays, 1 to 1600 (default 52; the record starts in 1997); until (YYYY-MM-DD) ends the period in that week instead of the latest, so weeks=78 with until=2009-06-30 is the 2008 crisis. every is week (default), month or quarter, one reading per period (its last Friday); more than 160 readings step up to months, then quarters.

Input parameters:

- `every` (string)
- `until` (string)
- `weeks` (integer)

### `get_tremor_breaks` (~138 tokens)

Get tremor breaks

New breaks in the last four weeks of the Antevo Tremor Index, newest first and most unusual first: pairs whose correlation crossed two standard deviations from its own previous two years for the first time after thirteen weeks without a break the same way. Each with its week, the two markets, the family, the direction (strengthening: moving closer; weakening: coming apart), z and the correlation. family narrows to one of Equity regions, US sectors, Credit, Bonds, Commodities, FX and crypto, Volatility; direction to strengthening or weakening.

Input parameters:

- `direction` (string)
- `family` (string)

### `get_tremor_pairs` (~206 tokens)

Get tremor pairs

The pairs of one week of the Antevo Tremor Index, most unusual first: the two markets, the family, the correlation of weekly returns weighted to the last few months (half-life nine weeks), z against the pair's own previous two years (positive: moving closer than usual; negative: coming apart), the direction (strengthening, weakening, or holding below two standard deviations) and the plain 26- and 52-week correlations. week is any date (YYYY-MM-DD) in the week wanted, default the latest; breaking_only (default true) keeps pairs at two standard deviations or more; family narrows to one family; market keeps pairs naming that market (for example Gold, S&P 500, Bitcoin); limit 1 to 200 (default 25).

Input parameters:

- `breaking_only` (boolean)
- `family` (string)
- `limit` (integer)
- `market` (string)
- `week` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 66

## Common questions

### What is the Tremor Watch MCP server?

Tremor Watch is an MCP server listed in the public MCP registry as ch.antevo/tremor-watch. How many market relationships stopped behaving this week: the Antevo Tremor Index, since 1997. This page covers its hosted endpoint (https://api.antevo.ch/mcp/tremor/mcp).

### Is the Tremor Watch MCP server safe to use?

Tremor Watch scores 70 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 Tremor Watch MCP server expose?

Tremor Watch exposes 4 tools: get_tremor_index, get_tremor_history, get_tremor_breaks, get_tremor_pairs. Their descriptions and schemas cost roughly 698 tokens of context every time the server is loaded.

### Does the Tremor Watch MCP server require authentication?

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

### Is the Tremor Watch MCP server still maintained?

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

### What did VerifyMCP test on the Tremor Watch MCP server?

VerifyMCP ran 13 checks on Tremor Watch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.antevo.ch/mcp/tremor/mcp
- Repository: https://github.com/ANTEVO-CH/antevo-mcp
- Website: https://antevo.ch/tremor-watch/
- Changelog RSS feed: https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ch-antevo-tremor-watch/mcp-tremor-mcp