DataQuoll

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.dataquoll/data-api and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 6 Sept 2026. Not supplied by the maker.

• list_incidents

  Returns a GeoJSON FeatureCollection of all current emergency incidents, with support for filtering, pagination, and bounding box queries. Example response: { "type": "FeatureCollection", "feature

• get_incident

  Returns a single incident as a GeoJSON Feature.

• nearby_incidents

  Returns incidents within a radius (km) of a given lat/lng coordinate, sorted by distance.

• incident_snapshot

  Returns the incidents that were active at a specific point in time. Recent datetimes are reconstructed from live and lifecycle data. Datetimes before 2026-04-08 are reconstructed from the historical a

• list_historical_incidents

  Returns historical emergency incidents from the 4.8M+ record archive (1840-2026). Free tier is blocked. Starter tier limited to 1 year lookback, Developer and Business to 5 years, Pro and Enterprise u

• list_states

  Returns the status of each state feed, including last poll time, health, and incident count.

• declarations_by_postcode

  Returns the declaration STATUS for a postcode: declared, partial, activation_only, not_declared, uncertain, or unknown_postcode, with per-LGA detail and official source links. Reports declared-area st

• declarations_by_point

  Returns the declaration STATUS for the local government area containing a lat/lng point, resolved against ABS LGA 2022 (ASGS Edition 3) boundary polygons at full resolution. POST with a JSON body is u

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.