# Nasa Firms (npm · @pipeworx/mcp-nasa-firms)

NASA FIRMS MCP — active-fire / thermal-anomaly detections from MODIS and VIIRS.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-nasa-firms/nasa-firms-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-nasa-firms/nasa-firms-mcp)
- npm · `@pipeworx/mcp-nasa-firms`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-nasa-firms/pipeworx-mcp-nasa-firms.md), [page](https://verifymcp.io/servers/pipeworx-io-nasa-firms/pipeworx-mcp-nasa-firms)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-nasa-firms`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-nasa-firms).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-nasa-firms -- npx -y @pipeworx/mcp-nasa-firms
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-nasa-firms": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-nasa-firms"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-nasa-firms": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-nasa-firms"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-nasa-firms -- npx -y @pipeworx/mcp-nasa-firms
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-nasa-firms": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-nasa-firms"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-nasa-firms --command npx --arg -y --arg @pipeworx/mcp-nasa-firms
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-nasa-firms:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-nasa-firms"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-nasa-firms": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-nasa-firms"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-nasa-firms -t stdio -c npx -a -y @pipeworx/mcp-nasa-firms
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-nasa-firms": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-nasa-firms"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 80, +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.

### 2026-10-31 (score 79, +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.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `firms_hotspots_area` (~399 tokens)

"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.

Input parameters:

- `_apiKey` (string): Your FIRMS MAP_KEY. Free at https://firms.modaps.eosdis.nasa.gov/api/map_key/
- `bbox` (string, required): 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…

### `firms_hotspots_near` (~340 tokens)

"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.

Input parameters:

- `_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, required): Latitude in decimal degrees, -90 to 90.
- `limit` (number): Max detections to return (default 100, max 1000).
- `longitude` (number, required): 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…

### `firms_data_availability` (~125 tokens)

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".

Input parameters:

- `_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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-nasa-firms/pipeworx-mcp-nasa-firms#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 65
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-nasa-firms
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-nasa-firms
- Repository: https://github.com/pipeworx-io/mcp-nasa-firms
- Website: https://pipeworx.io/packs/nasa-firms
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-nasa-firms/pipeworx-mcp-nasa-firms.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-nasa-firms/pipeworx-mcp-nasa-firms.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-nasa-firms/pipeworx-mcp-nasa-firms