DataQuoll

io.dataquollPublished by dataquoll.ioOfficial publisherv1.7.1Updated Oct 24, 2026

Australian data as MCP tools: incidents, gauges, declarations, calendars, police releases, archive.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

DataQuoll exposes Australian public data — incidents, gauges, declarations, calendars, police releases and archives — as MCP tools over a remote endpoint.

What you can do
Retrieve Australian incident records and gauge readings through the hosted tools. Look up declarations, calendars and police releases. Search the archive for older Australian data. Access is through a single authenticated remote endpoint rather than a local package.
When to use it
Useful when an assistant needs Australian public-sector data such as incidents, river or other gauges, emergency declarations, calendars or police releases, and you want it without building your own data pipeline.
Requirements
A remote MCP endpoint at dataquoll.io using streamable HTTP. An OAuth-based API key is required, sent as a Bearer token in the Authorization header; free keys are offered at signup. Network access to the provider is needed.
Before you install
The server requires a secret API key in the Authorization header, so keep it out of shared logs and configuration. It is a hosted third-party service, so queries and any data you send go to the provider. No tool list was published, so confirm read versus write behavior before relying on it.

Installation

In SourceWeft

  1. Open DataQuoll in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.dataquoll%2Fdata-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dataquoll": {
      "type": "http",
      "url": "https://dataquoll.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.7.1LatestOct 12, 2026
  2. v1.7.0Oct 12, 2026
  3. v1.3.1Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.