mcpbeat Sign in

DataQuoll MCP Server

by dataquoll Your server? Claim it
answering

DataQuoll is answering right now. Last checked 6 min ago. It exposes 22 tools.

Australian public data as MCP tools: incidents, gauges, declarations, industry calendars, archive.

Uptime history 13 days of history · worst day 99%
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
22
Tools
read from the server
646 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

7 Sep 3 tools appeared get_calendar_day, get_calendar_days, list_calendars
7 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check DataQuoll every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add data-api --transport http https://dataquoll.io/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "data-api": {
      "url": "https://dataquoll.io/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.data-api]
url = "https://dataquoll.io/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "data-api": {
      "url": "https://dataquoll.io/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "data-api": {
      "url": "https://dataquoll.io/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

declarations
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 used deliberately so coordinates never appear in URLs or request logs; the request is read-only and safe to retry. Coordinates are never stored, logged, or echoed back, and the response is Cache-Control: no-store. Reports declared-area status only; the billing decision rests with the practitioner. A point outside every Australian LGA returns unknown_location. A point exactly on a shared LGA boundary returns every covering area with onBoundary=true. LGA matching is at ABS code level; some ABS codes aggregate multiple administrative areas (for example Unincorporated NSW covers both Far West and Lord Howe Island). Requires the "declarations" entitlement on the API key. Accounts without it get a clear error rather than an empty result, so an empty response never means "not entitled".
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 status only; the billing/eligibility decision rests with the practitioner. Built for Medicare disaster telehealth checks. Requires the "declarations" entitlement on the API key. Accounts without it get a clear error rather than an empty result, so an empty response never means "not entitled".
list_declarations
Browse and historically report on declaration records. Filters and keyset (cursor) pagination. Record status is derived at query time. Requires the "declarations" entitlement on the API key. Accounts without it get a clear error rather than an empty result, so an empty response never means "not entitled".
gauge
get_gauge
Returns a single gauge station plus its trailing 6 hours of raw readings (enough to see the current trend). Deeper history is the tier-gated /gauges/{id}/readings endpoint.
get_gauge_summary
Counts of gauges at or above minor/moderate/major flood classification, grouped by state or LGA, plus the full list of at-or-above-minor stations (capped at 500). STALE GUARD: only readings within the staleness horizon enter class counts — a days-old reading above minor is counted as stale, never as a current flood signal.
list_gauge_readings
Historical water level readings for one gauge. Free tier is blocked (the free surface is current readings on /gauges and the 6-hour window on /gauges/{id}). Starter tier limited to 1 year lookback, Developer and Business to 5 years, Pro and Enterprise unlimited. Retention ladder: raw 30 days, hourly rollups 90 days, daily forever — plus full-resolution raw inside flood-event windows kept forever. interval=auto picks the finest granularity available for the requested window.
calendar
get_calendar_day
The answer for one date in one jurisdiction. A jurisdiction-wide public holiday wins, then the weekend, then the calendar's own entries in order (industry shutdown, RDO, part-day holiday, annual leave, industry event); otherwise working. Restricted holidays (a show day for one region, a public-service-only day) never decide it and are returned under restricted for the caller to apply to the employer's area.
get_calendar_days
The day rows for one jurisdiction across a date range, each date answered by exactly one edition. Defaults to the current calendar year in the jurisdiction's own time zone; a lone from or to extends to the edge of its own year. Every place the calendar disagrees with the official list is returned under discrepancies. Rows can be CSV with format=csv.
incident
get_incident
Returns a single incident as a GeoJSON Feature.
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 archive (4.8M+ records) and are gated by the same tier lookback as /incidents/history (free has no archive access; Starter 1 year, Developer and Business 5 years, Pro and Enterprise unlimited). Archive (pre-2026-04-08) snapshots require a state filter, and meta.source indicates whether the result came from "live" or "archive".
attribution
get_attribution
Returns attribution information for all data sources, including licence details. Required for CC BY compliance.
calendars
list_calendars
Every industry-calendar edition on the platform, one per jurisdiction and year (NSW, VIC, QLD, WA, SA, TAS, ACT and NT for 2026), with its publisher, cover range and per-category counts. RDOs, public holidays, school holidays and industry shutdowns, read from each branch calendar and verified against the Fair Work Ombudsman list and the education departments' term dates.
declaration
declaration_by_agrn
The declaration/activation for an Australian Government Reference Number, merged across sources with the full affected-LGA list. Requires the "declarations" entitlement on the API key. Accounts without it get a clear error rather than an empty result, so an empty response never means "not entitled".
event
get_event
Returns a single clustered event by ID. Use `include_incidents=true` to also retrieve all incidents that belong to this event cluster.
events
list_events
Returns spatially clustered emergency events as a GeoJSON FeatureCollection. Events group related incidents using PostGIS ST_ClusterDBSCAN spatial clustering. Each event has a boundary polygon, centroid, affected suburbs, contributing agencies, and auto-generated title and summary. Only active events are returned by default.
gauges
list_gauges
Returns river gauge stations with their latest water level, the Bureau of Meteorology flood classification thresholds for each gauge, and a derived floodClass (below_minor, minor, moderate, major, or unclassified) computed from the latest reading against the published thresholds. Water-level readings are in metres relative to each gauge's local datum (each gauge carries its own unit, since some report in AHD). readingStatus flags stale data (bom-kiwis sourced stations are a 1-2 day archive, stale horizon 72 hours; bcc-telemetry are event-driven council ALERT loggers, stale horizon 48 hours; telemetry sources 24 hours). Defaults to water-level gauges; pass variable=rainfall for observed rainfall gauges, which report incremental millimetres and carry no flood classification. Status reporting, not flood prediction.
hazard
hazard_history_by_point
What official sources recorded near a location, unioned with the disaster declarations that covered its local government area. Two lanes are returned because both are required: the observed lane (historical archive plus live-era incident history within a radius) and the declared lane (declarations for the covering ABS LGA, counted once per AGRN even when several authorities recorded the same event). Measured example: a Lismore address returns the February 2022 flood only through the declared lane, because the spatial lane holds no record for it at address precision. POST with a JSON body is used deliberately so coordinates never appear in URLs or request logs; the request is read-only and safe to retry. Coordinates are never stored, logged, or echoed back, and the response is Cache-Control: no-store. This reports a RECORD and a declared STATUS. It is not an assessment of risk, insurability, or any obligation, and absence of a record is not evidence that nothing happened. Precision is reported per record: a record at postcode precision sits at a postcode centroid, which can be kilometres from the event. Requires the "hazard-history" entitlement on the API key. Accounts without it get a clear error rather than an empty result, so an empty response never means "not entitled".
historical
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 unlimited.
incidents
list_incidents
Returns a GeoJSON FeatureCollection of all current emergency incidents, with support for filtering, pagination, and bounding box queries. Example response: { "type": "FeatureCollection", "features": [ { "type": "Feature", "id": "nsw-rfs-1234567", "geometry": { "type": "Point", "coordinates": [ 150.604, -33.883 ] }, "properties": { "source": { "state": "nsw", "agency": "RFS", "feedId": "1234567" }, "title": "Bush Fire - Warragamba", "eventType": "bushfire", "status": "active", "warningLevel": "watch_and_act", "severity": "Severe", "urgency": "Expected", "certainty": "Observed", "location": { "address": "Warragamba Dam Rd, Warragamba NSW", "suburb": "Warragamba", "state": "NSW", "latitude": -33.883, "longitude": 150.604 }, "details": { "description": "Bush fire burning in a south-easterly direction" }, "timestamps": { "reported": "2026-04-07T14:30:00+10:00", "updated": "2026-04-07T16:45:00+10:00", "fetched": "2026-04-07T16:46:12+10:00" }, "retraction": { "retracted": true, "retractedAt": "2026 ... (truncated)
nearby
nearby_incidents
Returns incidents within a radius (km) of a given lat/lng coordinate, sorted by distance.
schema
get_schema
Returns all valid enum values for event types, categories, states, warning levels, and other filterable fields. Use this to discover what values are accepted by filter parameters. No authentication required.
states
list_states
Returns the status of each state feed, including last poll time, health, and incident count.

Endpoints

URLTransportStateLatencyChecked
https://dataquoll.io/api/mcp streamable-http sign-in 487 ms 6 min ago

Alternatives to DataQuoll

same job, measured the same way
A
Aether Wealth
by aetherwealth

Aether Wealth MCP for AI assistants: trades, alerts, market data, macro calendar & indicators.

318 installs/wk local only
Datadog
by us-all

Datadog MCP — 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet

498 installs/wk local only
Logclaw MCP Server
by robeldev

Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.

37 installs/wk local only
Kronos Crypto Data
by hashchecked

Crypto data MCP: 22 tools covering derivatives, forecasts, alerts, liquidations, GEX — 16 assets.

67 installs/wk local only
Pagerduty
by mcparmory

Manage incidents, on-call schedules, escalation policies, and alert notifications

226 installs/wk local only
VMware Debug
by zw008

Read-only VMware incident correlation: timeline, spikes, root-cause routing. 2 MCP tools.

930 installs/wk local only
Rootly
by wyre-technology

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

local only
Rootly
by wyre-ai

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

local only

DataQuoll — questions

Answers built from our own checks of this server.

What can DataQuoll do?
It exposes 22 tools, read directly from the server on our last check. Among them: declaration_by_agrn, declarations_by_point, declarations_by_postcode, get_attribution, get_calendar_day, get_calendar_days and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is DataQuoll mostly used for?
Its tools cluster around declarations, gauge and incident. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is DataQuoll working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 646 ms. The bar chart above shows every period we have measured.
How do I connect DataQuoll?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to DataQuoll?
No API key is involved. DataQuoll answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is DataQuoll?
It answers our handshake in 646 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.