# ABS Data (observed) (remote · abs-data-front-door.aicolab.workers.dev) Australian Bureau of Statistics data: 1,227 tables, offering only options confirmed to serve data - Trust score: 68/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-29 ## Components - remote · `abs-data-front-door.aicolab.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/samjb123-abs-data/abs-data-front-door.md), [page](https://verifymcp.io/servers/samjb123-abs-data/abs-data-front-door) ## Channel facts - Endpoint: `https://abs-data-front-door.aicolab.workers.dev/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.1.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-29. - **Endpoint Security**: 46/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 81/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1544 tokens (~154/item across 10 items; 6 tools + 4 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 67/100 - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 89/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 61% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the ABS Data (observed) MCP server? ABS Data (observed) is a hosted endpoint at https://abs-data-front-door.aicolab.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http samjb123-abs-data 'https://abs-data-front-door.aicolab.workers.dev/mcp' ``` ### Cursor ```json { "mcpServers": { "samjb123-abs-data": { "url": "https://abs-data-front-door.aicolab.workers.dev/mcp" } } } ``` ### VS Code ```json { "servers": { "samjb123-abs-data": { "type": "http", "url": "https://abs-data-front-door.aicolab.workers.dev/mcp" } } } ``` ### Codex ```toml [mcp_servers.samjb123-abs-data] url = "https://abs-data-front-door.aicolab.workers.dev/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "samjb123-abs-data": { "type": "remote", "url": "https://abs-data-front-door.aicolab.workers.dev/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add samjb123-abs-data --url 'https://abs-data-front-door.aicolab.workers.dev/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: samjb123-abs-data: url: "https://abs-data-front-door.aicolab.workers.dev/mcp" ``` ### Netclaw ```json { "McpServers": { "samjb123-abs-data": { "Transport": "http", "Url": "https://abs-data-front-door.aicolab.workers.dev/mcp" } } } ``` ### Vellum ```bash assistant mcp add samjb123-abs-data -t streamable-http -u 'https://abs-data-front-door.aicolab.workers.dev/mcp' ``` ### Other ```json { "mcpServers": { "samjb123-abs-data": { "type": "http", "url": "https://abs-data-front-door.aicolab.workers.dev/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-29 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-28 (score 67, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-09-26 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-25 (score 66, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-09-24 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-22 (score 65, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-20 (score 64, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-18 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (6) ### `search_tables` (~187 tokens) Search ABS tables 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. Input parameters: - `frequency` (string): A annual, S semi-annual, Q quarterly, M monthly, W weekly, D daily - `geography` (string): Restrict to a geography level, e.g. SA2, LGA - `limit` (integer) - `query` (string): Free text over ids, names, topics, dimensions Output parameters: - `provenance` (object) - `results` (array) - `total` (integer) ### `describe_table` (~71 tokens) Describe a table 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. Input parameters: - `table` (string, required): Dataflow id, e.g. CPI Output parameters: - `dimensions` (array) - `exampleUrl` (string) - `keyFormat` (string): Dimension ids joined by '.', the order a selection is serialised in - `provenance` (object) - `table` (object) ### `search_options` (~76 tokens) Search a dimension's options 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. Input parameters: - `dimension` (string, required) - `limit` (integer) - `query` (string, required): Match against option codes and labels - `table` (string, required) Output parameters: - `options` (array) - `provenance` (object) - `total` (integer) ### `get_data` (~213 tokens) Get data 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. Input parameters: - `endPeriod` (string) - `firstN` (integer) - `lastN` (integer): Most recent N observations per series; default 12 when no period is given - `maxRows` (integer): Cap on returned observations - `select` (object): dimension id -> option code or label (or several). Omitted dimensions match everything. - `startPeriod` (string): e.g. 2020, 2020-Q1, 2020-03 - `table` (string, required) Output parameters: - `availabilityUrl` (string) - `fullDataUrl` (string) - `key` (string): The resolved selection as an SDMX key - `periodRange` (object) - `provenance` (object) - `rows` (array) - `rowsReturned` (integer) - `seriesMatched` (integer) - `table` (string) - `truncated` (boolean) ### `search` (~368 tokens) Search the catalogue by writing code 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; options: { literal: Record>; // codelist id -> { code: label } for small codelists (<=64 options) branded: Record; // large codelists -> option count (use abs.searchOptions in execute) }; } Input parameters: - `code` (string, required): JavaScript. `catalogue` is in scope. Must return a value. Output parameters: - `error` (string) - `logs` (array) - `ok` (boolean) - `result` - `truncated` (boolean) ### `execute` (~537 tokens) Fetch and analyse data by writing code 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; 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, dimens… Input parameters: - `code` (string, required): JavaScript. `abs` is in scope. Must return a value. Output parameters: - `error` (string) - `logs` (array) - `ok` (boolean) - `result` - `truncated` (boolean) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/samjb123-abs-data/abs-data-front-door#diagnostics ## Score history - 2026-09-29: 68 - 2026-09-28: 67 - 2026-09-27: 67 - 2026-09-26: 67 - 2026-09-25: 66 - 2026-09-24: 66 - 2026-09-23: 65 - 2026-09-22: 65 - 2026-09-21: 64 - 2026-09-20: 64 - 2026-09-19: 63 - 2026-09-18: 63 - 2026-09-17: 62 - 2026-09-16: 62 - 2026-09-15: 61 - 2026-09-14: 61 - 2026-09-13: 60 - 2026-09-12: 60 - 2026-09-11: 60 - 2026-09-10: 59 - 2026-09-09: 59 ## Common questions ### What is the ABS Data (observed) MCP server? ABS Data (observed) is an MCP server listed in the public MCP registry as io.github.SamJB123/abs-data. Australian Bureau of Statistics data: 1,227 tables, offering only options confirmed to serve data. This page covers its hosted endpoint (https://abs-data-front-door.aicolab.workers.dev/mcp). ### Is the ABS Data (observed) MCP server safe to use? ABS Data (observed) scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the ABS Data (observed) MCP server expose? ABS Data (observed) exposes 6 tools: search_tables, describe_table, search_options, get_data, search, execute. Their descriptions and schemas cost roughly 1,452 tokens of context every time the server is loaded. ### Does the ABS Data (observed) MCP server require authentication? No. We connected to ABS Data (observed) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the ABS Data (observed) MCP server still maintained? ABS Data (observed) is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://abs-data-front-door.aicolab.workers.dev/mcp - Repository: https://github.com/AI-CoLab/abs-data-mcp - Website: https://abs-data-front-door.aicolab.workers.dev/ - Changelog RSS feed: https://verifymcp.io/servers/samjb123-abs-data/abs-data-front-door.xml - Changelog JSON feed: https://verifymcp.io/servers/samjb123-abs-data/abs-data-front-door.json - HTML version of this page: https://verifymcp.io/servers/samjb123-abs-data/abs-data-front-door