mcp-registry/com.olyport/wildfire · v1.26.0
As of 2026-10-27 03:34 UTC, the Olyport Wildfire MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Active wildfire incidents from the National Interagency Fire Center
Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/wildfire/mcp
6 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.olyport%2Fwildfire/fixes
{
"name": "get_active_fires",
"description": "Get current active wildfire incidents from NIFC.\n\n Returns data on active wildfires including name, location, size, and\n containment status. Data is updated frequently during fire season.\n\n Args:\n state: Two-letter US state abbreviation to filter by (e.g. 'CA', 'OR').\n min_acres: Minimum fire size in acres to include (e.g. 100 for fires over 100 acres).\n limit: Maximum number of fires to return (default 50).\n ",
"inputSchema": {
"type": "object",
"title": "get_active_firesArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 50
},
"state": {
"type": "string",
"title": "State",
"default": null
},
"min_acres": {
"type": "number",
"title": "Min Acres",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_fire_perimeters",
"description": "Get fire perimeter data for active or recent wildfires.\n\n Returns perimeter boundaries and associated metadata. Useful for\n understanding the geographic extent of fires.\n\n Args:\n fire_name: Name of a specific fire to look up (case-insensitive partial match).\n state: Two-letter US state abbreviation to filter by.\n ",
"inputSchema": {
"type": "object",
"title": "get_fire_perimetersArguments",
"properties": {
"state": {
"type": "string",
"title": "State",
"default": null
},
"fire_name": {
"type": "string",
"title": "Fire Name",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_fire_stats",
"description": "Get wildfire statistics summary including total fires and acres burned.\n\n Returns aggregate statistics from active incident data. When no year is\n specified, returns current year statistics.\n\n Args:\n year: Year to get statistics for (e.g. 2025). Defaults to current year.\n ",
"inputSchema": {
"type": "object",
"title": "get_fire_statsArguments",
"properties": {
"year": {
"type": "integer",
"title": "Year",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.olyport/wildfire"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.olyport/wildfire"}) over MCP.
get_active_fires ~212 tokensget_fire_perimeters ~168 tokensget_fire_stats ~133 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fwildfire?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fwildfire?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fwildfire.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fwildfire.svg :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fwildfire?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:26c3bcaab8e2c3f2…, first seen 2026-10-17, included at leaf 14232 of 77,130. Version history · verify what your client received.
Compare: most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:34 UTC, the Olyport Wildfire MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Olyport Wildfire MCP server advertises 3 tools, including get_active_fires, get_fire_perimeters, get_fire_stats.
Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/wildfire/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.