Tremor Watch
REMOTE · API.ANTEVO.CH
How many market relationships stopped behaving this week: the Antevo Tremor Index, since 1997.
Available components
Last scanned (8 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.antevo.ch/mcp/tremor/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.antevo.ch | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 6 Aug 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | 909fd7f3310a15b23f9995e4159bbf0 |
| SANs: api.antevo.ch | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.antevo.ch. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ch. | DS published | 58745 | 13 | Verified |
| antevo.ch. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://*.vestai.ai https://api.vestai.ai https://*.ciamlogin.com https://*.clerk.accounts.dev |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.antevo.ch/mcp/tremor/mcp | Verified | 200 | |
| http (plaintext) | http://api.antevo.ch/mcp/tremor/mcp | HTTPS enforced | 301 | https://api.antevo.ch/mcp/tremor/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_tremor_breaks Get tremor breaks ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| family | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tremor_history Get tremor history ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| every | string | – | – |
| until | string | – | – |
| weeks | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tremor_index Get tremor index ~173
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_tremor_pairs Get tremor pairs ~206
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).
| Name | Type | Req | Description |
|---|---|---|---|
| breaking_only | boolean | – | – |
| family | string | – | – |
| limit | integer | – | – |
| market | string | – | – |
| week | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · api.antevo.ch
claude mcp add --transport http ch-antevo-tremor-watch 'https://api.antevo.ch/mcp/tremor/mcp'
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.