Nasa Firms
NPM · @PIPEWORX/MCP-NASA-FIRMS · 2 COMPONENTS
NASA FIRMS MCP — active-fire / thermal-anomaly detections from MODIS and VIIRS.
Available components
Last scanned (49 minutes ago)
Scores higher than 69% of npm servers
Category Maps and Location
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-firms). 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 919 tokens (~306/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
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 78
First indexed and scored.
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-firms@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-firms |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-nasa-firms/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655630164 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3bbd42c72a71ca70f1c1ccdd45c2e463ebd45fdab1254f75112ab5410876ca5216c50ba711202a6a59c545c443f9b4e233ee0ccfca9bc28e4ce841171 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
firms_data_availability ~125
Which dates each NASA FIRMS satellite product actually covers — the first and last date available per sensor, for near-real-time and standard-processing streams. Call this before querying a historical date so an empty hotspot result can be read as "outside the archive" rather than "no fires".
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your FIRMS MAP_KEY. Free at https://firms.modaps.eosdis.nasa.gov/api/map_key/ |
| source | string | – | A single product id (see firms_hotspots_area) or "ALL" for every sensor (default). |
No output schema declared.
No examples provided.
firms_hotspots_area ~399
"Where are the wildfires in California right now" / "active fire detections over Greece this week" — satellite thermal-anomaly (active fire) detections inside a bounding box, from NASA FIRMS. AUTHORITATIVE for where something is actually burning right now: these are pixels a MODIS or VIIRS sensor measured as hot, published within ~3 hours of overpass, not a news report about a fire. Returns latitude/longitude, acquisition date and UTC time, brightness temperature, fire radiative power (MW), confidence, satellite and day/night flag. PREFER OVER WEB SEARCH for current fire locations and extent.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your FIRMS MAP_KEY. Free at https://firms.modaps.eosdis.nasa.gov/api/map_key/ |
| bbox | string | yes | Bounding box as "west,south,east,north" in decimal degrees, e.g. "-125,32,-114,42" for California. Use "world" for the whole globe (large). Maximum extent -180,-90,180,90. |
| date | string | – | Start date YYYY-MM-DD. Omit for the most recent data. |
| day_range | number | – | Number of days to return, 1-5 (default 1). Counted forward from `date`, or backward from today when `date` is omitted. |
| limit | number | – | Max detections to return (default 200, max 2000). |
| source | string | – | Satellite product. "VIIRS_SNPP_NRT" (default, 375 m, global, near-real-time), "VIIRS_NOAA20_NRT", "VIIRS_NOAA21_NRT", "MODIS_NRT" (1 km, longest record), "LANDSAT_NRT" (30 m, US/Canada only), or the… |
No output schema declared.
No examples provided.
firms_hotspots_near ~340
"Are there any fires near Boulder, Colorado?" / "active fire detections within 50 km of this point" — NASA FIRMS satellite hotspot detections around a latitude/longitude, sorted nearest first with the distance in km. Same measured detections as firms_hotspots_area, addressed the way a question about a place is actually asked. Returns distance_km, position, acquisition time, brightness temperature, fire radiative power and confidence.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your FIRMS MAP_KEY. Free at https://firms.modaps.eosdis.nasa.gov/api/map_key/ |
| date | string | – | Start date YYYY-MM-DD. Omit for the most recent data. |
| day_range | number | – | Number of days to search, 1-5 (default 1). |
| latitude | number | yes | Latitude in decimal degrees, -90 to 90. |
| limit | number | – | Max detections to return (default 100, max 1000). |
| longitude | number | yes | Longitude in decimal degrees, -180 to 180. |
| radius_km | number | – | Search radius in km (default 100, max 500). |
| source | string | – | Satellite product. "VIIRS_SNPP_NRT" (default, 375 m, global, near-real-time), "VIIRS_NOAA20_NRT", "VIIRS_NOAA21_NRT", "MODIS_NRT" (1 km, longest record), "LANDSAT_NRT" (30 m, US/Canada only), or the… |
No output schema declared.
No examples provided.
How do I install the Nasa Firms MCP server?
Nasa Firms runs locally as an npm package, launched with npx -y @pipeworx/mcp-nasa-firms. 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-firms
claude mcp add pipeworx-io-nasa-firms -- npx -y @pipeworx/mcp-nasa-firms
What is the Nasa Firms MCP server?
Nasa Firms is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nasa-firms. NASA FIRMS MCP, active-fire / thermal-anomaly detections from MODIS and VIIRS. This page covers its npm package (@pipeworx/mcp-nasa-firms).
Is the Nasa Firms MCP server safe to use?
Nasa Firms 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 Firms MCP server expose?
Nasa Firms exposes 3 tools: firms_hotspots_area, firms_hotspots_near, firms_data_availability. Their descriptions and schemas cost roughly 864 tokens of context every time the server is loaded.
Is the Nasa Firms MCP server still maintained?
Nasa Firms 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 Firms MCP server under?
Nasa Firms declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.