ABS Data (observed)
Server Details
Australian Bureau of Statistics data: 1,227 tables, offering only options confirmed to serve data
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AI-CoLab/abs-data-mcp
- GitHub Stars
- 0
- Server Listing
- ABS Data API MCP Server
TDQS
Score is being calculated.
Available Tools
6 toolsdescribe_tableDescribe a tableInspect
A table's dimensions in key order, its coverage dates, and its observed options. Dimensions with up to 64 options list them inline with labels; larger ones (geography, occupations) say how many and are searchable with search_options.
| Name | Required | Description | Default |
|---|---|---|---|
| table | Yes | Dataflow id, e.g. CPI |
Output Schema
| Name | Required | Description |
|---|---|---|
| table | Yes | |
| keyFormat | Yes | Dimension ids joined by '.', the order a selection is serialised in |
| dimensions | Yes | |
| exampleUrl | Yes | |
| provenance | Yes |
executeFetch and analyse data by writing codeInspect
Run JavaScript in an isolated sandbox whose only capability is abs, a client with the same four verbs as this server (searchTables, describeTable, searchOptions, getData) and the same guarantees: every selection is verified against ABS before fetching. Use it for multi-series or multi-table analysis — fetch several series, compute growth rates, rank capitals, join tables — and return only the computed result, so large payloads never reach the conversation. No network beyond abs. Budgets: 10s CPU, 50 calls, 25s wall clock, 200KB result. Your code runs inside an async function; use await; console.log is captured.
// The abs object available in execute():
interface Abs {
searchTables(input: { query?: string; geography?: string; frequency?: "A"|"S"|"Q"|"M"|"W"|"D"; limit?: number }):
Promise<{ results: TableSummary[]; total: number }>;
describeTable(table: string):
Promise<{ table: TableSummary; dimensions: { id: string; position: number; optionCount: number; options?: { code: string; label: string|null }[] }[]; keyFormat: string }>;
searchOptions(input: { table: string; dimension: string; query: string; limit?: number }):
Promise<{ options: { code: string; label: string|null; parent?: string|null }[]; total: number }>;
getData(input: { table: string; select?: Record<string, string|string[]>; startPeriod?: string; endPeriod?: string; lastN?: number; firstN?: number; maxRows?: number }):
Promise<{ key: string; rows: { series: string; period: string; value: number|null; unit?: string|null }[]; rowsReturned: number; truncated: boolean; seriesMatched: number; fullDataUrl: string }>;
}
interface TableSummary { id: string; name: string|null; seriesCount: number; frequencies: string[]; coverage: { from: string|null; to: string|null }; dimensions: string[]; family: string|null; geography: string|null; matchedOptions?: { dimension: string; code: string; label: string|null }[] }
// getData throws an Error whose message is JSON: { reason, dimension, message, validOptions?, alternatives? } — catch it, read validOptions, correct and retry.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | JavaScript. `abs` is in scope. Must return a value. |
Output Schema
| Name | Required | Description |
|---|---|---|
| ok | Yes | |
| logs | Yes | |
| error | No | |
| result | No | |
| truncated | No |
get_dataGet dataInspect
Fetch observations. select maps dimension ids to option codes or labels (several allowed); omitted dimensions match everything. The selection is verified live against ABS before fetching, so a call that succeeds always returns real data. Returns up to maxRows observations (default 500, most recent 12 periods per series unless a period range is given), a summary, and the URL for the complete pull. If an option or combination does not exist you are asked to choose from the valid ones.
| Name | Required | Description | Default |
|---|---|---|---|
| lastN | No | Most recent N observations per series; default 12 when no period is given | |
| table | Yes | ||
| firstN | No | ||
| select | No | dimension id -> option code or label (or several). Omitted dimensions match everything. | |
| maxRows | No | Cap on returned observations | |
| endPeriod | No | ||
| startPeriod | No | e.g. 2020, 2020-Q1, 2020-03 |
Output Schema
| Name | Required | Description |
|---|---|---|
| key | Yes | The resolved selection as an SDMX key |
| rows | Yes | |
| table | Yes | |
| truncated | Yes | |
| provenance | Yes | |
| fullDataUrl | Yes | |
| periodRange | Yes | |
| rowsReturned | Yes | |
| seriesMatched | Yes | |
| availabilityUrl | Yes |
searchSearch the catalogue by writing codeInspect
Run JavaScript against the whole catalogue document — every table, its dimensions, coverage and small-dimension options — in an isolated sandbox with no network. Use it to answer questions the fixed verbs make awkward: 'which tables have both an SA2 geography and a quarterly frequency?', 'list every dimension name and how often it appears', 'find codelists whose labels mention rent'. Your code runs inside an async function with catalogue in scope; return a JSON-serialisable value; console.log output is captured.
// The catalogue object available in search():
interface Catalogue {
provenance: { runId: string; observedAt: string };
corpus: { tables: number; seriesConfirmed: number; seriesImpliedByMetadata: number; density: number };
tables: Record<string, { // keyed by table id, e.g. catalogue.tables.CPI
id: string; name: string|null; description: string|null; seriesCount: number;
frequencies: string[]; coverage: { from: string|null; to: string|null }; density: number|null;
family: string|null; geography: string|null; topics: string[];
dimensions: { id: string; position: number; codelist: string|null; optionCount: number; literal: boolean }[];
}>;
options: {
literal: Record<string, Record<string, string|null>>; // codelist id -> { code: label } for small codelists (<=64 options)
branded: Record<string, number>; // large codelists -> option count (use abs.searchOptions in execute)
};
}
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | JavaScript. `catalogue` is in scope. Must return a value. |
Output Schema
| Name | Required | Description |
|---|---|---|
| ok | Yes | |
| logs | Yes | |
| error | No | |
| result | No | |
| truncated | No |
search_optionsSearch a dimension's optionsInspect
Find option codes by label text within one dimension of one table — e.g. a suburb name in a geography dimension. Returns codes to use in get_data's select.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | Match against option codes and labels | |
| table | Yes | ||
| dimension | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| total | Yes | |
| options | Yes | |
| provenance | Yes |
search_tablesSearch ABS tablesInspect
Find ABS statistical tables (dataflows) by topic words, geography level or frequency. Matches table names, topics and dimension names, and also option labels inside dimensions — a search for 'rent' finds CPI through its INDEX option 'Rents' and reports the match in matchedOptions. Census tables published at several geography levels are collapsed to one result with familyGeographies listing the others (use the geography filter to pick one). Every result is confirmed to serve data — nothing here comes from documentation alone. Start here, then describe_table.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Free text over ids, names, topics, dimensions | |
| frequency | No | A annual, S semi-annual, Q quarterly, M monthly, W weekly, D daily | |
| geography | No | Restrict to a geography level, e.g. SA2, LGA |
Output Schema
| Name | Required | Description |
|---|---|---|
| total | Yes | |
| results | Yes | |
| provenance | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
6 tool updates
- First observed
describe_table - First observed
execute - First observed
get_data - First observed
search - First observed
search_options - First observed
search_tables
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
A wide range of validated governmental statistics and datasets for Australia, NZ, US, Argentina, Uraguay
UK Office for National Statistics dataset catalogue + Beta JSON API
Australian Bureau of Statistics (ABS) Data API MCP.
MCP server for Statistics Sweden (SCB) - 1200+ tables with population, economy, environment data
Related MCP Servers
- FlicenseCqualityFmaintenanceProvides access to the Australian Bureau of Statistics (ABS) Data API. This server allows AI assistants to query and analyze ABS statistical data.19-
- AlicenseAqualityBmaintenanceCited Australian stats via the ausdata.io gateway — stable AU.* series IDs, source_url + retrieved_at on every response. Free tier. Not a data broker; upgrade for Embed / signed / webhooks.28881MIT
- AlicenseAqualityCmaintenanceMIT ABS sister MCP — same five tools, citations. Pair with the ausdata gateway for joins and Embed.71MIT
- AlicenseAqualityAmaintenanceMCP server for structured Australian macroeconomic and financial data from the Australian Bureau of Statistics (ABS), the Reserve Bank of Australia (RBA), and the Australian Prudential Regulation Authority (APRA).144MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.