Australian Bureau of Statistics (ABS) Data API MCP.
MCPpedia last refreshed this data
io.github.pipeworx-io/abs-au is an MCP server that australian Bureau of Statistics (ABS) Data API MCP. Its tool list has not been published yet over http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"abs-au": {
"url": "https://gateway.pipeworx.io/abs-au/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Australian Bureau of Statistics (ABS) Data API MCP.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-abs-au against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in analytics
Ask your agent about your own Apple Health data: 194 metrics, 21 tools, local, 0 deps.
MCP server for Dynatrace Managed to access logs, events, and metrics.
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Read and manage Churnkey cancel flows, retention metrics, and payment recovery
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/abs-au and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Australian Bureau of Statistics (ABS) Data API MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1861+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
| Tool | Description |
|---|---|
list_dataflows | Browse or search ABS datasets (dataflows). Returns dataflow IDs + descriptive names; the ID (e.g. "CPI", "ALC", "ABS_REGIONAL_LGA2021") is what you pass to dataflow_structure and get_data. Optionally filter by a case-insensitive substring against the ID and name. |
dataflow_structure | For one ABS dataflow, return its ordered dimensions and the valid codes for each. Use this to build a dataKey for get_data: the key has one dot-separated position per dimension, in the order returned here. Call this before get_data. |
get_data | Fetch observations from an ABS dataflow. dataKey is a dot-separated SDMX filter with one position per dimension (order from dataflow_structure); each position is a code, "+"-joined codes, or empty for wildcard. Pass "all" to fetch everything (can be large). Returns decoded series with their dimension labels and time-indexed values. Fetch dataflow_structure first to learn the dimension order and valid codes. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"abs-au": {
"url": "https://gateway.pipeworx.io/abs-au/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/abs-au/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1861+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/abs_au_list_dataflows \
-H 'Content-Type: application/json' \
-d '{"search":"consumer price"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/abs_au_list_dataflows. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-abs-au is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/abs-au/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"abs-au": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-abs-au"]
}
}
}
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer to