Australian government open data republished as CSV, Excel, JSON, Parquet, SQLite, DuckDB, GeoJSON and GeoPackage at URLs that never change. Every release is a dated version that keeps its content, with schema, provenance and a diff. Run by National Digital. No government agency has endorsed it. Tools: - Search datasets: Find the slug of a served dataset. - Read a dataset: Read a served dataset's data package and full version history: licence, attribution, whole-table files and the version dates diff_versions and the version parameter take. - List a dataset's fields: List a served dataset's fields, with their types, descriptions, ranges and values, before querying it. - List partition files: List the download files that split a served dataset's newest version by one field, such as one file per year. - Query rows: Read individual rows of a served dataset, filtered across the whole table. - Count and sum rows: Count, sum, average, minimum or maximum rows of a served dataset across the whole table, grouped by up to three fields. - Compare versions: Compare two consecutive versions of a served dataset row by row on its key fields, to see what a publisher changed between releases. - Search government portals: Search every dataset listed on Australia's government portals, including the many publicdata.au does not serve yet. - List the build backlog: List the datasets people have asked publicdata.au to build, most votes first. - Vote for a dataset: Add one anonymous vote for a government dataset that publicdata.au does not serve yet, so it is built sooner. The fields of one dataset by slug: types, the publisher's descriptions, ranges and the values each field holds. Find slugs with search_datasets or resources/list. The MCP server logs the methods, tools and client software of each request, and leaves out the address and the arguments' values. To keep the rate limit, it counts row tool calls per address in Cloudflare's cache for 10 seconds.

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	23/25	Endpoint answers the MCP initialize handshake (5275 ms); very slow response -2.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 12 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Very slow (5275 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 80% of peers; This listing 86 · peer median 81
Latency: Faster than 18% of peers; This listing 669 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (5275 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-09-29 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/national-digital/publicdata-au/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/national-digital/publicdata-au/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://publicdata.au/

Listed at (smithery)

https://publicdata.au/