Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Geomagnetic Storms X

REMOTE · MCP.CAFFEINE-SOFT.COM

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

+4 this week 70 Trust /100

Last scanned (17 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 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.

  • 17 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.

  • 15 Nov 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.

  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 65

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.caffeine-soft.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caffeine-soft.com CN=WE1,O=Google Trust Services,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA256 6e0f7f894424042138c263ef0378496
SANs: caffeine-soft.com, mcp.caffeine-soft.com, *.mcp.caffeine-soft.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.caffeine-soft.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
caffeine-soft.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.caffeine-soft.com/mcp Verified 200
http (plaintext) http://mcp.caffeine-soft.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~913 tokens

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 →

Tool Tokens
get_geomagnetic_now ~138

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.

NameTypeReqDescription
timeZonestring–IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.
NameTypeReqDescription
forecastIssuedAtstring|nullyesWhen NOAA issued the 3-day forecast used, UTC.
generatedAtstringyesWhen this answer was produced, UTC.
nextStorm–yesThe next storm in the NOAA 3-day forecast that has not ended; null if none.
reading–yesThe newest Kp value; null if none has been received yet.
sourcesarrayyesWhere the data comes from and on what terms.
stalebooleanyesTrue when the data service was unreachable and this is the last copy received.
summaryobjectyesThe forecast in one sentence, as the Geomagnetic Storms X apps say it.
timeZonestringyesThe IANA time zone every local time here is in.

No examples provided.

get_kp_forecast_3day ~141

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.

NameTypeReqDescription
timeZonestring–IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.
NameTypeReqDescription
daysarrayyesToday and the two days after it in the requested time zone.
generatedAtstringyes–
intervalsarrayyesThe three-hour intervals across the three local days, in time order.
issuedAtstring|nullyesWhen NOAA issued the forecast, UTC.
nextStorm–yes–
sourcesarrayyesWhere the data comes from and on what terms.
stalebooleanyesTrue when the data service was unreachable and this is the last copy received.
summaryobjectyesThe forecast in one sentence, as the Geomagnetic Storms X apps say it.
timeZonestringyesThe IANA time zone the days and local times are in.

No examples provided.

get_kp_history ~185

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.

NameTypeReqDescription
periodstring–24h: hourly peaks; 7d: three-hourly values; 30d: daily peaks. Defaults to 24h. The service keeps 30 days.
timeZonestring–IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.
NameTypeReqDescription
generatedAtstringyes–
max–yesThe highest value of the period and when.
missingCountintegeryesHow many of the values have nothing measured.
periodstringyes–
resolutionstringyesHow long each value covers.
sourcesarrayyesWhere the data comes from and on what terms.
stalebooleanyes–
stormCountintegeryesHow many of the values reached a storm, G1 or above.
timeZonestringyes–
valuesarrayyesOldest first.

No examples provided.

get_moon_phase ~174

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.

NameTypeReqDescription
datestring–A calendar date, YYYY-MM-DD, in the given time zone. Defaults to today there.
timeZonestring–IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.
NameTypeReqDescription
ageDaysnumberyesDays since the last new moon.
atstringyesThe moment the illumination and age describe: now for today, local noon for another date. UTC.
datestringyesThe local calendar date described, YYYY-MM-DD.
illuminationPercentintegeryesThe lit share of the disc, 0 to 100.
isWaxingbooleanyes–
nextFullMoonobjectyes–
nextNewMoonobjectyes–
phasestringyesWhat the day is called: the phase whose moment falls on it, or the crescent or gibbous moon after the last one.
phaseNamestringyes–
phasesThisMontharrayyesNew moon, first quarter, full moon and last quarter in the local calendar month of the date.
sourcesarrayyesWhere the data comes from and on what terms.
timeZonestringyes–

No examples provided.

get_outlook_27day ~100

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
daysarrayyesFrom the current UTC day to the end of the outlook.
generatedAtstringyes–
issuedAtstringyesWhen NOAA issued the outlook, UTC. It is reissued weekly.
sourcesarrayyesWhere the data comes from and on what terms.
stalebooleanyes–

No examples provided.

get_solar_flares ~175

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.

NameTypeReqDescription
hours––How far back to look: 24, 72 or 168 hours. Defaults to 24.
timeZonestring–IANA time zone of the person asking, such as Europe/Moscow or America/New_York. Local times and days use it. Defaults to UTC.
NameTypeReqDescription
flaresarrayyesFlares that began in the period, newest first.
flaresTruncatedbooleanyesTrue when only the 100 most recent flares are listed and older ones in the period are left out.
generatedAtstringyes–
hoursintegeryes–
peak–yesThe highest X-ray flux of the period; at is the start of its 5-minute bucket for 24 hours, its hour for longer periods.
sourcesarrayyesWhere the data comes from and on what terms.
stalebooleanyes–
summarystringyes–
timeZonestringyes–
xrayNow–yes–

No examples provided.

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.

remote · mcp.caffeine-soft.com

# add to Claude Code
claude mcp add --transport http caffeine-soft-geomagnetic-storms-x 'https://mcp.caffeine-soft.com/mcp'
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.