au-bushfire-nsw-mcp MCP server

Settings → Connectors → Add custom connector, then paste:
https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp

{
  "mcpServers": {
    "au-bushfire-nsw-mcp": {
      "url": "https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp"
    }
  }
}

{
  "servers": {
    "au-bushfire-nsw-mcp": {
      "type": "http",
      "url": "https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp"
    }
  }
}

code --add-mcp '{"name":"au-bushfire-nsw-mcp","type":"http","url":"https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp"}'

claude mcp add --transport http au-bushfire-nsw-mcp https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp

{
  "mcpServers": {
    "au-bushfire-nsw-mcp": {
      "type": "streamableHttp",
      "url": "https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

{
  "mcpServers": {
    "au-bushfire-nsw-mcp": {
      "httpUrl": "https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp"
    }
  }
}

[mcp_servers.au-bushfire-nsw-mcp]
url = "https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp"

{
  "context_servers": {
    "au-bushfire-nsw-mcp": {
      "url": "https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp"
    }
  }
}

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://au-bushfire-nsw-mcp.donniertf.workers.dev/mcp --transport http

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Facts about the publisher. We do not turn them into a trust score.

Source: the registry entry and api.github.com · 2026-10-30.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

No session

No session could be opened when we tried, so no check could run. No security score is given; a check we did not run is never counted as passed.

Why not security-tested: The server limited how often we could connect; that reflects our batch of tests, not a problem with the server. — our limit

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). None of the 18 checks that apply to it could be exercised. We do not publish security-check outcomes for named servers.

Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

The steps in order, as the test record holds them.

1. 0 msStarted a session with the server's remote endpoint
2. No session could be opened.
3. 267 msFinished: 0 checks exercised.

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.