mcpbeat

NIFC Wildfire Data MCP Server

com.olyport/wildfire
answering

NIFC Wildfire Data is answering right now. Last checked 14 min ago. It exposes 3 tools.

Active wildfire incidents from the National Interagency Fire Center

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
532 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add wildfire --transport http https://mcp.olyport.com/wildfire/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "wildfire": {
      "url": "https://mcp.olyport.com/wildfire/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.wildfire]
url = "https://mcp.olyport.com/wildfire/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wildfire": {
      "url": "https://mcp.olyport.com/wildfire/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "wildfire": {
      "url": "https://mcp.olyport.com/wildfire/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fire
get_fire_perimeters
Get fire perimeter data for active or recent wildfires. Returns perimeter boundaries and associated metadata. Useful for understanding the geographic extent of fires. Args: fire_name: Name of a specific fire to look up (case-insensitive partial match). state: Two-letter US state abbreviation to filter by.
get_fire_stats
Get wildfire statistics summary including total fires and acres burned. Returns aggregate statistics from active incident data. When no year is specified, returns current year statistics. Args: year: Year to get statistics for (e.g. 2025). Defaults to current year.
active
get_active_fires
Get current active wildfire incidents from NIFC. Returns data on active wildfires including name, location, size, and containment status. Data is updated frequently during fire season. Args: state: Two-letter US state abbreviation to filter by (e.g. 'CA', 'OR'). min_acres: Minimum fire size in acres to include (e.g. 100 for fires over 100 acres). limit: Maximum number of fires to return (default 50).

Endpoints

URLTransportStateLatencyChecked
https://mcp.olyport.com/wildfire/mcp streamable-http answering 517 ms 14 min ago

NIFC Wildfire Data — questions

Answers built from our own checks of this server.

What can NIFC Wildfire Data do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_active_fires, get_fire_perimeters, get_fire_stats. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is NIFC Wildfire Data working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 532 ms. The bar chart above shows every period we have measured.
How do I connect NIFC Wildfire Data?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does NIFC Wildfire Data need an API key?
No. NIFC Wildfire Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is NIFC Wildfire Data?
It answers our handshake in 532 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.