_ registry / mcp http-sse · checked 59m ago

solarstorm

https://mcp.solarstorm.today

Registry code: ae78a11b7a2def25

api record

Space weather: Kp index, NOAA 3-day geomagnetic forecast, solar flares, aurora visibility.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.solarstorm.today/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is solarstorm live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is solarstorm free to use?
Yes — the hub reached it with no key and no payment.
What tools does solarstorm have?
4 tools: get_aurora_visibility, get_current_kp, get_solar_flares_24h, get_kp_forecast_3day.
Is solarstorm safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.8%· all time 99.8%

latency
90ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 590 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
weather & environment
used for
  • get current kp index
  • get 3-day geomagnetic forecast
  • check aurora visibility for a latitude
  • get solar flare activity
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_current_kp reads open 11h ago

    Current planetary Kp index: latest value, level (low/moderate/high/severe) and the observed 24-hour maximum.

    mcp-tool

    {
  "type": "object",
  "title": "get_current_kpArguments",
  "properties": {}
}
    arguments 5 lines
  • get_solar_flares_24h reads open 11h ago

    Solar X-ray activity of the past 24 hours from GOES: current flare class and the 24-hour peak class.

    mcp-tool

    {
  "type": "object",
  "title": "get_solar_flares_24hArguments",
  "properties": {}
}
    arguments 5 lines
  • get_kp_forecast_3day reads open 11h ago

    Official NOAA 3-day geomagnetic forecast: the maximum expected Kp per calendar day (Europe/Berlin days).

    mcp-tool

    {
  "type": "object",
  "title": "get_kp_forecast_3dayArguments",
  "properties": {}
}
    arguments 5 lines
  • get_aurora_visibility reads unknown 4h ago

    Aurora visibility outlook for a geographic latitude (degrees, e.g. 48.2 for Vienna): the Kp you need there, the expected maximum Kp in the next 24 h, and a verdict.

    mcp-tool

    {
  "type": "object",
  "title": "get_aurora_visibilityArguments",
  "required": [
    "latitude"
  ],
  "properties": {
    "latitude": {
      "type": "number",
      "title": "Latitude"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ae78a11b7a2def25.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ae78a11b7a2def25/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ae78a11b7a2def25/badge.svg)](https://brick.blue/agent/ae78a11b7a2def25?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.