Connect NIFC Wildfire Data and your agent gets 3 tools, among them get_active_fires, get_fire_perimeters, get_fire_stats. It answers at https://mcp.olyport.com/wildfire/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Active wildfire incidents from the National Interagency Fire Center
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: state, min_acres, limit |
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 par Inputs: fire_name, state |
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). Inputs: year |
Every block below points at https://mcp.olyport.com/wildfire/mcp. Pick your client and copy.
claude mcp add --transport http nifc-wildfire-data https://mcp.olyport.com/wildfire/mcp
{
"mcpServers": {
"nifc-wildfire-data": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.olyport.com/wildfire/mcp"]
}
}
}{
"mcpServers": {
"nifc-wildfire-data": {
"url": "https://mcp.olyport.com/wildfire/mcp"
}
}
}{
"servers": {
"nifc-wildfire-data": {
"type": "http",
"url": "https://mcp.olyport.com/wildfire/mcp"
}
}
}{
"context_servers": {
"nifc-wildfire-data": {
"url": "https://mcp.olyport.com/wildfire/mcp"
}
}
}{
"mcpServers": {
"nifc-wildfire-data": {
"serverUrl": "https://mcp.olyport.com/wildfire/mcp"
}
}
}{
"mcpServers": {
"nifc-wildfire-data": {
"url": "https://mcp.olyport.com/wildfire/mcp"
}
}
}name: NIFC Wildfire Data
version: 0.0.1
schema: v1
mcpServers:
- name: NIFC Wildfire Data
type: streamable-http
url: https://mcp.olyport.com/wildfire/mcp{
"mcpServers": {
"nifc-wildfire-data": {
"httpUrl": "https://mcp.olyport.com/wildfire/mcp"
}
}
}{
"mcpServers": {
"nifc-wildfire-data": {
"type": "http",
"url": "https://mcp.olyport.com/wildfire/mcp"
}
}
}{
"mcpServers": {
"nifc-wildfire-data": {
"url": "https://mcp.olyport.com/wildfire/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.olyport.com%2Fwildfire%2Fmcp&type=streamable_http&id=nifc-wildfire-data&name=NIFC%20Wildfire%20Data
It answered our last check on 18 October 2026 in 507 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by olyport.com and served from mcp.olyport.com, the vendor's own domain: https://mcp.olyport.com/wildfire/mcp.
3, as returned by the server's own tools/list on 31 August 2026: get_active_fires, get_fire_perimeters, get_fire_stats.
It answered our last check on 18 October 2026 in 507 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.olyport.com/wildfire/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.olyport. Endpoint host: mcp.olyport.com. ARD identifier: urn:air:com.olyport:mcp:wildfire.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.