# Geomagnetic Storms X (remote · mcp.caffeine-soft.com)

Magnetic storms: Kp now, NOAA G1-G5, 3- and 27-day forecasts, history, solar flares, Moon.

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

## Components

- remote · `mcp.caffeine-soft.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp.md), [page](https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp)

## Channel facts

- Endpoint: `https://mcp.caffeine-soft.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-11-21.

- **Endpoint Security**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1134 tokens (~189/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Geomagnetic Storms X MCP server?

Geomagnetic Storms X is a hosted endpoint at https://mcp.caffeine-soft.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 caffeine-soft-geomagnetic-storms-x 'https://mcp.caffeine-soft.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "caffeine-soft-geomagnetic-storms-x": {
      "url": "https://mcp.caffeine-soft.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "caffeine-soft-geomagnetic-storms-x": {
      "type": "http",
      "url": "https://mcp.caffeine-soft.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.caffeine-soft-geomagnetic-storms-x]
url = "https://mcp.caffeine-soft.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "caffeine-soft-geomagnetic-storms-x": {
      "type": "remote",
      "url": "https://mcp.caffeine-soft.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add caffeine-soft-geomagnetic-storms-x --url 'https://mcp.caffeine-soft.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  caffeine-soft-geomagnetic-storms-x:
    url: "https://mcp.caffeine-soft.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "caffeine-soft-geomagnetic-storms-x": {
      "Transport": "http",
      "Url": "https://mcp.caffeine-soft.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add caffeine-soft-geomagnetic-storms-x -t streamable-http -u 'https://mcp.caffeine-soft.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "caffeine-soft-geomagnetic-storms-x": {
      "type": "http",
      "url": "https://mcp.caffeine-soft.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-11-21 (score 70, +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-19 (score 69, +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-17 (score 68, +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-11-15 (score 67, +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-11-13 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 65)

First indexed and scored.

## MCP tools (6)

### `get_geomagnetic_now` (~138 tokens)

Geomagnetic conditions now

Answers "is there a magnetic storm now / today?", "what is the Kp index?", "how is space weather?". The current planetary K index (Kp) and NOAA G-scale storm level, when it was observed and whether it is still current, the next storm in the NOAA 3-day forecast, and a one-sentence summary. Data from NOAA SWPC and GFZ Potsdam. Geophysical data only; no health information.

Input parameters:

- `timeZone` (string): IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.

Output parameters:

- `forecastIssuedAt` (string|null): When NOAA issued the 3-day forecast used, UTC.
- `generatedAt` (string): When this answer was produced, UTC.
- `nextStorm`: The next storm in the NOAA 3-day forecast that has not ended; null if none.
- `reading`: The newest Kp value; null if none has been received yet.
- `sources` (array): Where the data comes from and on what terms.
- `stale` (boolean): True when the data service was unreachable and this is the last copy received.
- `summary` (object): The forecast in one sentence, as the Geomagnetic Storms X apps say it.
- `timeZone` (string): The IANA time zone every local time here is in.

### `get_kp_forecast_3day` (~141 tokens)

Kp forecast for the next 3 days

Answers "will there be a magnetic storm tomorrow?", "geomagnetic forecast for the next days", "when does the storm start?". NOAA's 3-day planetary K index forecast laid over today, tomorrow and the day after in the asker's time zone: each day's peak, every three-hour interval (measured once it has begun, forecast after), the next storm and a one-sentence summary. Geophysical data only; no health information.

Input parameters:

- `timeZone` (string): IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.

Output parameters:

- `days` (array): Today and the two days after it in the requested time zone.
- `generatedAt` (string)
- `intervals` (array): The three-hour intervals across the three local days, in time order.
- `issuedAt` (string|null): When NOAA issued the forecast, UTC.
- `nextStorm`
- `sources` (array): Where the data comes from and on what terms.
- `stale` (boolean): True when the data service was unreachable and this is the last copy received.
- `summary` (object): The forecast in one sentence, as the Geomagnetic Storms X apps say it.
- `timeZone` (string): The IANA time zone the days and local times are in.

### `get_outlook_27day` (~100 tokens)

27-day geomagnetic outlook

Answers "magnetic storms next week / this month", "any storms expected on a given date?". NOAA's 27-day outlook: for each day the largest expected Kp and its storm level, the expected Ap index and 10.7 cm radio flux. Days are UTC calendar dates, as NOAA issues them. Reissued weekly; a coarse outlook, not a day-by-day forecast. Geophysical data only; no health information.

Output parameters:

- `days` (array): From the current UTC day to the end of the outlook.
- `generatedAt` (string)
- `issuedAt` (string): When NOAA issued the outlook, UTC. It is reissued weekly.
- `sources` (array): Where the data comes from and on what terms.
- `stale` (boolean)

### `get_kp_history` (~185 tokens)

Kp history

Answers "were there magnetic storms yesterday / this week / this month?", "what was the strongest storm lately?". What the planetary K index did over the last 24 hours (hourly peaks of the NOAA estimate), 7 days (three-hourly values) or 30 days (daily peaks), in the asker's time zone, with the maximum and how many values reached a storm. Gaps are null, not zero. Geophysical data only; no health information.

Input parameters:

- `period` (string): 24h: hourly peaks; 7d: three-hourly values; 30d: daily peaks. Defaults to 24h. The service keeps 30 days.
- `timeZone` (string): IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.

Output parameters:

- `generatedAt` (string)
- `max`: The highest value of the period and when.
- `missingCount` (integer): How many of the values have nothing measured.
- `period` (string)
- `resolution` (string): How long each value covers.
- `sources` (array): Where the data comes from and on what terms.
- `stale` (boolean)
- `stormCount` (integer): How many of the values reached a storm, G1 or above.
- `timeZone` (string)
- `values` (array): Oldest first.

### `get_solar_flares` (~175 tokens)

Solar flares and X-rays

Answers "were there solar flares today?", "was there an X-class flare?", "is the Sun active?". The GOES X-ray level now (and whether it is current), the strongest X-ray flux of the last 24, 72 or 168 hours with its NOAA radio blackout level, and the solar flares NOAA recorded in that time: class, begin, peak and end, and whether one is in progress. Times in the asker's time zone. Data from NOAA SWPC.

Input parameters:

- `hours`: How far back to look: 24, 72 or 168 hours. Defaults to 24.
- `timeZone` (string): IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.

Output parameters:

- `flares` (array): Flares that began in the period, newest first.
- `flaresTruncated` (boolean): True when only the 100 most recent flares are listed and older ones in the period are left out.
- `generatedAt` (string)
- `hours` (integer)
- `peak`: The highest X-ray flux of the period; at is the start of its 5-minute bucket for 24 hours, its hour for longer periods.
- `sources` (array): Where the data comes from and on what terms.
- `stale` (boolean)
- `summary` (string)
- `timeZone` (string)
- `xrayNow`

### `get_moon_phase` (~174 tokens)

Moon phase

Answers "what is the moon phase today?", "when is the next full moon / new moon?". The Moon on a day in the asker's calendar: what the day is called (new moon, waxing crescent, first quarter and so on), how much of the disc is lit, its age, the next full and new moon, and the four main phases of that month, in local time. Computed with Meeus and checked against US Naval Observatory tables; useful for planning aurora watching.

Input parameters:

- `date` (string): A calendar date, YYYY-MM-DD, in the given time zone. Defaults to today there.
- `timeZone` (string): IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.

Output parameters:

- `ageDays` (number): Days since the last new moon.
- `at` (string): The moment the illumination and age describe: now for today, local noon for another date. UTC.
- `date` (string): The local calendar date described, YYYY-MM-DD.
- `illuminationPercent` (integer): The lit share of the disc, 0 to 100.
- `isWaxing` (boolean)
- `nextFullMoon` (object)
- `nextNewMoon` (object)
- `phase` (string): What the day is called: the phase whose moment falls on it, or the crescent or gibbous moon after the last one.
- `phaseName` (string)
- `phasesThisMonth` (array): New moon, first quarter, full moon and last quarter in the local calendar month of the date.
- `sources` (array): Where the data comes from and on what terms.
- `timeZone` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 65

## Common questions

### What is the Geomagnetic Storms X MCP server?

Geomagnetic Storms X is an MCP server listed in the public MCP registry as io.github.caffeine-soft/geomagnetic-storms-x. Magnetic storms: Kp now, NOAA G1-G5, 3- and 27-day forecasts, history, solar flares, Moon. This page covers its hosted endpoint (https://mcp.caffeine-soft.com/mcp).

### Is the Geomagnetic Storms X MCP server safe to use?

Geomagnetic Storms X 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 Geomagnetic Storms X MCP server expose?

Geomagnetic Storms X exposes 6 tools: get_geomagnetic_now, get_kp_forecast_3day, get_outlook_27day, get_kp_history, get_solar_flares, get_moon_phase. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.

### Does the Geomagnetic Storms X MCP server require authentication?

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

### Is the Geomagnetic Storms X MCP server still maintained?

Geomagnetic Storms X 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 Geomagnetic Storms X MCP server?

VerifyMCP ran 12 checks on Geomagnetic Storms X, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Geomagnetic Storms X: HTTPS. 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://mcp.caffeine-soft.com/mcp
- Website: https://spacewx.caffeine-soft.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp.json
- HTML version of this page: https://verifymcp.io/servers/caffeine-soft-geomagnetic-storms-x/mcp
