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.

Nasa Gibs

NPM · @PIPEWORX/MCP-NASA-GIBS · 2 COMPONENTS

NASA GIBS MCP — the satellite-imagery layer catalogue behind Worldview.

+3 this week 81 Trust /100

Last scanned (10 hours ago)

Scores higher than 69% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-nasa-gibs). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 887 tokens (~295/item across 3 items; 3 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 Management23
  • Stability observed for 7 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 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.

  • 30 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 78

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-nasa-gibs@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-nasa-gibs
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-nasa-gibs/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3655634503
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6c3bd7495cf2ff2ac034f8be9c2910d208fba7eaef7c10eb47f399ea4c2b100182f5cd57671532dd4551949951d185e2a8c318a7658f66ce2ab32431c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~832 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
gibs_layer_info ~198

Everything NASA GIBS publishes about one imagery layer: its full title, the dates it actually covers (as ISO 8601 start/end/period ranges), the most recent date available, native tile grid and zoom depth, image format, geographic extent, colour map and legend URLs, and the raw WMTS tile template. Call this before gibs_tile_url when you need to know which dates exist for a layer.

NameTypeReqDescription
layerstringyesGIBS layer identifier, e.g. "MODIS_Terra_CorrectedReflectance_TrueColor". Get one from gibs_list_layers.
projectionstring–Tile projection: "epsg4326" (geographic lat/lon, default), "epsg3857" (Web Mercator, the Leaflet/Google tile scheme), "epsg3413" (Arctic polar), "epsg3031" (Antarctic polar).

No output schema declared.

No examples provided.

gibs_list_layers ~261

"What NASA satellite imagery layers are there for wildfires / sea ice / aerosols?" — search NASA GIBS, the ~1,300-layer imagery catalogue behind NASA Worldview. AUTHORITATIVE for which global satellite imagery products exist and what time span each covers: true-colour MODIS/VIIRS mosaics, thermal anomalies, sea-surface temperature, aerosol optical depth, snow and ice cover, vegetation index, night lights. Returns each layer's identifier (the id the other two tools take), human title, resolution grid, image format and the date range it is available for.

NameTypeReqDescription
limitnumber–Max layers to return (default 40, max 300).
projectionstring–Tile projection: "epsg4326" (geographic lat/lon, default), "epsg3857" (Web Mercator, the Leaflet/Google tile scheme), "epsg3413" (Arctic polar), "epsg3031" (Antarctic polar).
querystring–Case-insensitive substring matched against layer title and identifier, e.g. "fires", "sea ice", "VIIRS_SNPP_CorrectedReflectance". Omit to list the whole catalogue.

No output schema declared.

No examples provided.

gibs_tile_url ~373

"Give me the satellite image of Los Angeles on 2026-09-10" — build a ready-to-fetch NASA GIBS image tile URL for a layer, a date and a place. Give a latitude/longitude and a zoom level and it computes the WMTS tile row/column for you; give tile_row/tile_col directly if you already have them. Returns the tile URL plus the tile's own geographic bounds and the resolved date, so the caller can show or download the actual imagery.

NameTypeReqDescription
datestring–Date YYYY-MM-DD. Omit to use the layer's most recent available date.
latitudenumber–Latitude of the point the tile should cover. Required unless tile_row/tile_col are given.
layerstringyesGIBS layer identifier, e.g. "VIIRS_NOAA20_CorrectedReflectance_TrueColor".
longitudenumber–Longitude of the point the tile should cover.
projectionstring–Tile projection: "epsg4326" (geographic lat/lon, default), "epsg3857" (Web Mercator, the Leaflet/Google tile scheme), "epsg3413" (Arctic polar), "epsg3031" (Antarctic polar). Latitude/longitude are c…
tile_colnumber–WMTS tile column, if you already know it.
tile_rownumber–WMTS tile row, if you already know it (alternative to latitude/longitude).
zoomnumber–Zoom level / TileMatrix, 0 = whole globe. Default 4. Capped at the layer's deepest level.

No output schema declared.

No examples provided.

Install

How do I install the Nasa Gibs MCP server?

Nasa Gibs runs locally as an npm package, launched with npx -y @pipeworx/mcp-nasa-gibs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-nasa-gibs

# add to Claude Code
claude mcp add pipeworx-io-nasa-gibs -- npx -y @pipeworx/mcp-nasa-gibs
Common questions

What is the Nasa Gibs MCP server?

Nasa Gibs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nasa-gibs. NASA GIBS MCP, the satellite-imagery layer catalogue behind Worldview. This page covers its npm package (@pipeworx/mcp-nasa-gibs).

Is the Nasa Gibs MCP server safe to use?

Nasa Gibs scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Nasa Gibs MCP server expose?

Nasa Gibs exposes 3 tools: gibs_list_layers, gibs_layer_info, gibs_tile_url. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.

Is the Nasa Gibs MCP server still maintained?

Nasa Gibs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Nasa Gibs MCP server under?

Nasa Gibs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.