# ShockAtlas (remote · shockatlas.com)

Economic exposure to climate and geopolitical shocks: signals, data series, reviewed dossiers.

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

## Components

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

## Channel facts

- Endpoint: `https://shockatlas.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-21.

- **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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1590 tokens (~159/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 35% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

ShockAtlas is a hosted endpoint at https://shockatlas.com/api/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-shockatlas-atlas 'https://shockatlas.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-shockatlas-atlas": {
      "url": "https://shockatlas.com/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-shockatlas-atlas]
url = "https://shockatlas.com/api/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-shockatlas-atlas:
    url: "https://shockatlas.com/api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-shockatlas-atlas": {
      "type": "http",
      "url": "https://shockatlas.com/api/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-20 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_offers” rewrote its description, which is the text the model reads

### 2026-11-18 (score 74, +1)

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

### 2026-11-16 (score 73, +1)

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

### 2026-11-14 (score 72, +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-12 (score 71, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1272 → 1526
- [functional] New tool “get_watch”

### 2026-11-11 (score 71, +1)

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

### 2026-11-09 (score 70, +1)

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

### 2026-11-08 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (10)

### `list_signals` (~168 tokens)

List the published signals

Every published signal: slug, title, date, mechanism, geography codes, series keys with whether their values are redistributable, counts of organisations and hypotheses, the edition title, a summary of the reviewed dossier (verdict, counts, contradicted links) and the URLs to read it. Each signal has its place in the classification tree (domain › sector › chain); the tree itself, with the sectors not covered yet, comes back as taxonomy. Optional filters: q (text in title or slug), mechanism, geography (ISO code), domain and filiere (the sector id; ids from the tree).

Input parameters:

- `domain` (string)
- `filiere` (string)
- `geography` (string)
- `mechanism` (string)
- `q` (string)

### `get_signal` (~133 tokens)

Read one signal

The same object as /api/atlas/<slug>: the signal, every series with its provenance, licence and observations (the last twelve without a key, all of them with a member key), the edition's vectors, figures and watch list, the dated hypotheses, the organisations with their verbatim evidence, the reasoning dossier under analysis (public part, or complete with a member key), the offers, and an access block saying which of the two you got.

Input parameters:

- `key` (string): A member key (dfk1…), issued with the plan; omit it for the free sample
- `slug` (string, required)

### `get_edition` (~76 tokens)

Read the edition of a signal

The published edition in full: title, lead, the "In 30 seconds" brief when the edition has one, the three vectors, the text blocks with each paragraph labelled FACT, HYPOTHESIS or SCENARIO, the indicators to watch, and the figures recomputed at build time.

Input parameters:

- `slug` (string, required)

### `get_dossier` (~135 tokens)

Read the reasoning dossier of a signal

The dossier. Without a key, a preview: the question, the causal chain as link ends with a status per link (observed, consistent, untested, contradicted), two constants with their source quotes, the review verdict, and counts for the rest (constants, constraints, alternatives, conjectures, trajectories). A member key opens the complete dossier: every constant, bounded constraints, alternatives with their discriminators, checks, falsifiers, paths and implications.

Input parameters:

- `key` (string): A member key (dfk1…), issued with the plan; omit it for the free sample
- `slug` (string, required)

### `get_series` (~120 tokens)

Read one data series

One series with its publisher, source URL, SHA-256 of the collected file, licence (rights) and observations: the last twelve without a key (sample: true, observations_total says how many exist), all of them with a member key. A restricted series returns observations_withheld: true and no values for everyone: read it at source_url.

Input parameters:

- `key` (string, required)
- `member_key` (string): A member key (dfk1…), issued with the plan; omit it for the free sample
- `slug` (string, required)

### `get_export` (~94 tokens)

Export one signal (members)

With a member key: three signed links, valid seven days, to the complete export of one signal (bundle.json with the full dossier, counter-analysis and every series; organisations.csv; series.csv). Without a key it answers MEMBER_KEY_REQUIRED with the Premium plan.

Input parameters:

- `key` (string): A member key (dfk1…), issued with the plan; omit it for the free sample
- `slug` (string, required)

### `get_organisation` (~61 tokens)

Read one organisation across signals

An organisation named in the atlas and every documented exposure it has, across signals: direction (exposed, beneficiary, competitor, adjacent), evidenced or deduced, decision type, and the dated verbatim quote it rests on.

Input parameters:

- `slug` (string, required)

### `get_offers` (~65 tokens)

What is for sale

What is for sale and how a person pays: one analysis as files, paid once (a checkout link per analysis that you can hand to your user), and Premium, 49 USD per month, every published analysis with a member key. An agent cannot pay by itself here.

### `subscribe_newsletter` (~129 tokens)

Subscribe an address to the free weekly

Asks the free weekly edition for one email address. The address receives a single confirmation link and nothing else until its owner clicks it (double opt-in); one request per address per hour. Call it only for a person who asked to receive the editions, and say so with consent: true. The paid plan cannot be subscribed here: get_offers.premium.subscribe_url is where a person signs in and subscribes.

Input parameters:

- `consent` (boolean, required): true: the owner of this address asked for the editions
- `email` (string, required): The address of the person who asked for the free weekly

### `get_watch` (~178 tokens)

Read the standing collection points

Public gauges and trigger feeds read live from their publishers and refreshed every three hours, independent of any analysis: river levels on the Rhine, Danube, Elbe and Mississippi, flow on the Rhône, the official Mississippi stage forecast, orange and red disaster alerts (GDACS) and US sanctions and export-control documents (Federal Register). Without a key each point answers with its latest daily value and its change over seven days; a member key adds thirty daily values and the forecast. Optional filter: group (Rhine, Danube, Elbe, Mississippi, Rhône). Each point names its publisher and licence under sources; a point whose source did not answer carries an error and no value.

Input parameters:

- `group` (string)
- `key` (string): A member key (dfk1…), issued with the plan; omit it for the free sample

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70
- 2026-11-09: 70
- 2026-11-08: 69
- 2026-11-07: 69

## Common questions

### What is the ShockAtlas MCP server?

ShockAtlas is an MCP server listed in the public MCP registry as com.shockatlas/atlas. Economic exposure to climate and geopolitical shocks: signals, data series, reviewed dossiers. This page covers its hosted endpoint (https://shockatlas.com/api/mcp).

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

ShockAtlas 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 ShockAtlas MCP server expose?

ShockAtlas exposes 10 tools: list_signals, get_signal, get_edition, get_dossier, get_series, and 5 more. Their descriptions and schemas cost roughly 1,159 tokens of context every time the server is loaded.

### Does the ShockAtlas MCP server require authentication?

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

### Is the ShockAtlas MCP server still maintained?

ShockAtlas is still listed as active in the MCP registry. We last reached this channel on 21 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 ShockAtlas MCP server?

VerifyMCP ran 13 checks on ShockAtlas, 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://shockatlas.com/api/mcp
- Repository: https://github.com/H2-CO3/shockatlas
- Website: https://shockatlas.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-shockatlas-atlas/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-shockatlas-atlas/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-shockatlas-atlas/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-shockatlas-atlas/api-mcp
