abs-data
https://abs-data-front-door.aicolab.workers.dev
Registry code: 7891fa48d3d1cf30
Australian Bureau of Statistics data: 1,227 tables, offering only options confirmed to serve data
from a public catalogue that lists it, not from the operator
- endpoint
- https://abs-data-front-door.aicolab.workers.dev/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is abs-data live?
- Yes — it answered the hub's last check (checked 43m ago). It answered 99% of checks over the last 30 days.
- Is abs-data free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does abs-data have?
- 6 tools: execute, get_data, describe_table, search, search_options, search_tables.
- Is abs-data safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.9%· all time 98.9%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· fetch failed
- degraded → live
- used for
- search australian bureau of statistics tables
- get abs statistical data
- describe a statistics table's dimensions
- find option codes for a region
- takes → gives
- text, code → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_tables reads open 43m ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1 }, "query": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Free text over ids, names, topics, dimensions" }, "frequency": { "enum": [ "A", "S", "Q", "M", "W", "D" ], "type": "string", "description": "A annual, S semi-annual, Q quarterly, M monthly, W weekly, D daily" }, "geography": { "type": "string", "description": "Restrict to a geography level, e.g. SA2, LGA" } } }arguments 34 linesexecute reads unknown never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "code" ], "properties": { "code": { "type": "string", "maxLength": 20000, "minLength": 1, "description": "JavaScript. `abs` is in scope. Must return a value." } } }arguments 15 linesget_data reads unknown 9h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "table" ], "properties": { "lastN": { "type": "integer", "maximum": 1000, "minimum": 1, "description": "Most recent N observations per series; default 12 when no period is given" }, "table": { "type": "string", "minLength": 1 }, "firstN": { "type": "integer", "maximum": 1000, "minimum": 1 }, "select": { "type": "object", "default": {}, "description": "dimension id -> option code or label (or several). Omitted dimensions match everything.", "propertyNames": { "type": "string" }, "additionalProperties": { "anyOf": [ { "type": "string" }, { "type": "array", "items": { "type": "string" }, "minItems": 1 } ] } }, "maxRows": { "type": "integer", "default": 500, "maximum": 2000, "minimum": 1, "description": "Cap on returned observations" }, "endPeriod": { "type": "string" }, "startPeriod": { "type": "string", "description": "e.g. 2020, 2020-Q1, 2020-03" } } }arguments 60 linesdescribe_table reads unknown 9h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "table" ], "properties": { "table": { "type": "string", "minLength": 1, "description": "Dataflow id, e.g. CPI" } } }arguments 14 linessearch reads unknown 43m ago
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) }; }
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "code" ], "properties": { "code": { "type": "string", "maxLength": 20000, "minLength": 1, "description": "JavaScript. `catalogue` is in scope. Must return a value." } } }arguments 15 linessearch_options reads unknown 43m ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "table", "dimension", "query" ], "properties": { "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1 }, "query": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Match against option codes and labels" }, "table": { "type": "string", "minLength": 1 }, "dimension": { "type": "string", "minLength": 1 } } }arguments 31 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7891fa48d3d1cf30.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7891fa48d3d1cf30/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7891fa48d3d1cf30?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.