Is the Daedalmap Wildfires MCP server down?

mcp-registry/com.daedalmap/wildfires · v0.4.0

Verdict. Daedalmap Wildfires MCP server answered 98.23% of Glimind's liveness checks over 30 days, better than 5% of MCP servers, with 313 ms median handshake and 243 outages in 90 days. Its agent-readiness grade is A (92/100) across 5 tools, costing an agent about 1,949 tokens to load. Checked every few minutes; no tool is ever called.

Data as of .

30-day measurements and how they compare with other MCP servers
MetricValueBetter than
Uptime, 30 days98.23%5% of MCP servers
Median handshake latency313 ms61% of MCP servers
p95 handshake latency3006 ms—
Checks in 30 days5,036—
Outages, 90 days243—
Median recovery5 min—
Agent-readiness score92/100 (A)73% of MCP servers
Tools5—
Tool-list size for an agent~1,949 tokens53% of MCP servers
Days observed29—
healthy
Last checked 2026-10-27 00:34 UTC · handshake 196ms

As of 2026-10-27 00:34 UTC, the Daedalmap Wildfires MCP server is up with a Glimind reliability score of 68/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 244 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
98.2%
checks observed
5,052
outages (90d)
244
tools
5

Wildfire events and aggregates across global, U.S., and Canada sources. Paid via x402 USDC.

Install Daedalmap Wildfires MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http daedalmap-wildfires-mcp-server https://app.daedalmap.com/mcp/wildfires

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "daedalmap-wildfires-mcp-server": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/wildfires"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (92/100)

A (92/100): 0 error(s), 2 warning(s) across 5 tool(s); ~1,949 tokens of tool definitions.
Scores higher than 73% of 15,774 MCP servers Glimind has audited.
Its tool list costs an agent ~1,949 tokens per session — lighter than 55% of servers.
89 → 92 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions76
Safety hints100
Token cost100
Client compatibility100
Protocol100
Reliability75
Stability84

What to fix (3)

1 parameter(s) across 1 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 →

Tools: get_data

Reachable 98.2% of the time over the last 30 days; median recovery 5 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

In the last 30 days: 0 tool(s) removed and 4 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

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.daedalmap/wildfires"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.daedalmap/wildfires"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.daedalmap%2Fwildfires.svg)](https://glimind.com/server/mcp-registry%2Fcom.daedalmap%2Fwildfires?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.daedalmap%2Fwildfires?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.daedalmap%2Fwildfires.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.daedalmap%2Fwildfires.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.daedalmap%2Fwildfires?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3cd143df5a1e02b7…, first seen 2026-10-17, included at leaf 14957 of 76,376. Version history · verify what your client received.

Tools (5)

Compare: most reliable knowledge servers · most reliable data servers · most reliable other servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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

FAQ

Is the Daedalmap Wildfires MCP server down right now?

As of 2026-10-27 00:34 UTC, the Daedalmap Wildfires MCP server is up with a Glimind reliability score of 68/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 244 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Daedalmap Wildfires MCP server provide?

Daedalmap Wildfires MCP server advertises 5 tools, including get_catalog, get_data, get_event, get_pack, get_tool_help.

How do I install Daedalmap Wildfires MCP server?

Point your MCP client at this streamable-http endpoint: https://app.daedalmap.com/mcp/wildfires

Is the Daedalmap Wildfires MCP server safe to connect to an AI agent?

Glimind scanned all 5 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.

Operator of Daedalmap Wildfires MCP server?

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.

Feedback
Help us improve