Skip to main content
Glama

Server Details

NOAA Space Weather Prediction Center (solar wind, Kp, aurora, alerts)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-noaa-swpc
GitHub Stars
0
Server Listing
mcp-noaa-swpc

TDQS

A3.7/5.0

Scored across 38 tools

Disambiguation3/5

The router family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) is explicitly near-identical, and the Polymarket cluster (edges, arbitrage, kalshi_spread, edge_tracker, bet_research, fill_risk) plus the entity tools (resolve_entity, entity_profile, compare_entities, recent_changes) heavily overlap in purpose. Descriptions are extremely detailed and do draw boundaries, but an agent must read paragraphs to choose correctly, and _beta openly admits it currently duplicates the stable router.

Naming Consistency4/5

Nearly everything is snake_case, which is a strong baseline, but the conventions vary: verb_noun (resolve_entity, validate_claim), noun-only (alerts, solar_wind, kp_index), and prefixed families (ask_pipeworx*, polymarket_*). It is readable and mostly predictable, just not a single uniform pattern.

Tool Count2/5

38 tools is well above the comfortable 3-15 band and past the 25+ heavy threshold, even for a broad data aggregator. Several tools are redundant variants (router trio, multiple Polymarket scanners), meaning the surface is larger than the distinct capability set warrants.

Completeness5/5

The set covers a full lifecycle across its domains: discovery (discover_tools, suggest_questions, pipeworx_trending), research and lookup, entity resolution, memory CRUD (remember/recall/forget), subscription lifecycle (subscribe/list/unsubscribe/recent_alerts), and a feedback channel. Few obvious dead ends, and graceful-degradation notes are documented per tool.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
  2. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
        -  "company"
        -]New value: +[
        +  "company",
        +  "ticker"
        +]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  3. 1 tool update
    • Changedsolar_wind3 fields changed
      • changedOutput schema / properties / plasma / properties / measurements / items / properties / proton_vx_gse / type
        Previous value: -"number"New value: +[
        +  "number",
        +  "null"
        +]
      • changedOutput schema / properties / plasma / properties / measurements / items / properties / proton_vy_gse / type
        Previous value: -"number"New value: +[
        +  "number",
        +  "null"
        +]
      • changedOutput schema / properties / plasma / properties / measurements / items / properties / proton_vz_gse / type
        Previous value: -"number"New value: +[
        +  "number",
        +  "null"
        +]

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides real-time NOAA space weather data (solar flares, Kp index, solar wind) and analyzes HF radio propagation conditions for amateur radio operators to determine optimal frequency bands.
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Provides AI assistants with access to real-time space weather data and forecasts from NOAA's Space Weather Prediction Center, enabling queries and interpretations of geomagnetic storms, solar flares, and related indices.
    7
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    MCP server for space weather and HF propagation conditions — live solar flux, Kp index, DSCOVR solar wind, X-ray flux, alerts, 27-day forecast, and band-by-band outlook through any MCP-compatible AI assistant.
    7
    2
    GPL 3.0
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.