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 Cmr

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

NASA CMR (Common Metadata Repository) MCP.

+3 this week 83 Trust /100

Last scanned (8 hours ago)

Scores higher than 76% of npm servers

Category Education and Research

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-cmr). 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 Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 561 tokens (~187/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 +16
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 80

    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-cmr@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-cmr
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-nasa-cmr/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3655622829
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:33726023575ecbf089778feadbc4ffb75d5ef3db050f45310500161fb6d8fd6127b1ac313a479507f07a84a8f9554637f4e6e7ca1900af769ff76bb78

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 · ~506 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_collection ~92

Get full metadata for one NASA Earth-science collection by its CMR concept ID — summary, DOI/landing page, spatial coverage, temporal range, and access links. Keyless.

NameTypeReqDescription
concept_idstringyesCMR collection concept ID, e.g. "C1748058432-LPCLOUD" (MODIS/Terra Land Surface Temperature MOD11A1). Get IDs from search_collections.

No output schema declared.

No examples provided.

search_collections ~257

Search NASA's Common Metadata Repository for Earth-science dataset collections by keyword, platform (satellite/mission), instrument, time range, or bounding box. ~10k collections covering MODIS, Landsat, Sentinel, VIIRS, GPM, and every NASA DAAC. Sorted by usage. Keyless.

NameTypeReqDescription
bounding_boxstring–Spatial filter "minLon,minLat,maxLon,maxLat", e.g. "-125,32,-114,42" for California.
instrumentstring–Instrument name, e.g. "MODIS", "OLI", "VIIRS", "ASTER".
keywordstring–Free-text keyword, e.g. "aerosol", "sea surface temperature", "land cover".
limitnumber–Max results (default 10, max 25).
platformstring–Platform (satellite/mission) name, e.g. "Terra", "Landsat-9", "Sentinel-1A", "Suomi-NPP".
temporal_endstring–End of temporal filter, YYYY-MM-DD.
temporal_startstring–Start of temporal filter, YYYY-MM-DD. Collections overlapping the range match.

No output schema declared.

No examples provided.

search_granules ~157

List the individual data files (granules) of a NASA collection — newest first, with timestamps, file size, and direct download URLs. Filter by time range or bounding box. Keyless.

NameTypeReqDescription
bounding_boxstring–Spatial filter "minLon,minLat,maxLon,maxLat".
concept_idstringyesCMR collection concept ID, e.g. "C1748058432-LPCLOUD". Get IDs from search_collections.
limitnumber–Max results (default 10, max 25).
temporal_endstring–End of temporal filter, YYYY-MM-DD.
temporal_startstring–Start of temporal filter, YYYY-MM-DD. Granules overlapping the range match.

No output schema declared.

No examples provided.

Install

How do I install the Nasa Cmr MCP server?

Nasa Cmr runs locally as an npm package, launched with npx -y @pipeworx/mcp-nasa-cmr. 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-cmr

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

What is the Nasa Cmr MCP server?

Nasa Cmr is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nasa-cmr. NASA CMR (Common Metadata Repository) MCP. This page covers its npm package (@pipeworx/mcp-nasa-cmr).

Is the Nasa Cmr MCP server safe to use?

Nasa Cmr scores 83 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 Cmr MCP server expose?

Nasa Cmr exposes 3 tools: search_collections, get_collection, search_granules. Their descriptions and schemas cost roughly 506 tokens of context every time the server is loaded.

Is the Nasa Cmr MCP server still maintained?

Nasa Cmr 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 Cmr MCP server under?

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