firms_data_availability

Pack: nasa-firms · Endpoint: https://gateway.pipeworx.io/nasa-firms/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/firms_data_availability for the schema, then POST the same URL with its arguments for the data.

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

Parameters

Example call

Arguments

{
  "source": "ALL",
  "_apiKey": "your-firms-map-key"
}

curl

curl -X POST https://gateway.pipeworx.io/nasa-firms/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"firms_data_availability","arguments":{"source":"ALL","_apiKey":"your-firms-map-key"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('firms_data_availability', {
  "source": "ALL",
  "_apiKey": "your-firms-map-key"
});

More examples

{
  "source": "VIIRS_SNPP_NRT",
  "_apiKey": "your-firms-map-key"
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "nasa-firms": {
      "url": "https://gateway.pipeworx.io/nasa-firms/mcp"
    }
  }
}

See Getting Started for client-specific install steps.