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
Available components
Last scanned (22 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2572 tokens (~214/item across 12 items; 8 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “describe_table” rewrote its description, which is the text the model reads security
- Tool “search_tables” rewrote its description, which is the text the model reads security
- Schema quality: 154 → 214 ▼ functional
- Destructive annotations: 0% → 50% ▲ functional
- Tool coverage: 61% → 83% ▲ functional
- The server now declares the “completions” capability functional
- Schema quality: excellent → good functional
- New prompt “report_issue” functional
- New tool “feedback_form” functional
- New tool “submit_feedback” functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Oct 26 0
- Stability: 0.83 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://abs-data-front-door.aicolab.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aicolab.workers.dev | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e4ccaff3bc7b4de13cde6b965af9cfa |
| SANs: aicolab.workers.dev, *.aicolab.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of abs-data-front-door.aicolab.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://abs-data-front-door.aicolab.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://abs-data-front-door.aicolab.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_table Describe a table ~70
A table's dimensions in key order, its coverage dates, and its 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 | Type | Req | Description |
|---|---|---|---|
| table | string | yes | Dataflow id, e.g. CPI |
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | yes | – |
| exampleUrl | string | yes | – |
| keyFormat | string | yes | Dimension ids joined by '.', the order a selection is serialised in |
| provenance | object | yes | – |
| table | object | yes | – |
No examples provided.
execute Fetch and analyse data by writing code ~537
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, dimens…
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript. `abs` is in scope. Must return a value. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| logs | array | yes | – |
| ok | boolean | yes | – |
| result | – | – | – |
| truncated | boolean | – | – |
No examples provided.
feedback_form Open a feedback form ~410
Open a feedback form for the person, prefilled with your draft, so they can report a problem or suggest an improvement to this ABS connector — or flag something wrong in ABS's own data. Use it whenever the person wants to give feedback, or agrees when you offer after something went wrong. Fill in what you know from the conversation: kind, a one-line summary in their words, details, and the tool, table, selection and error involved. Never include personal information about anyone, and never fill in a contact email the person did not give you. This tool sends nothing: on hosts that show interactive views the person reviews, edits and sends the form themselves; elsewhere, follow the `next` field.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | connector: this connector or its site; abs: ABS's own data or API (so it can be passed on to ABS) |
| assistant | string | – | The AI tool in use, e.g. Claude, ChatGPT, Copilot |
| contact | string | – | Only if the person chose to give an email address for a reply. Never guess or fill one in. |
| details | string | – | What happened and what was expected. No personal information about anyone. |
| error | string | – | The error reason or message returned, if any |
| kind | string | – | bug: something broke; data: a figure or label looks wrong; missing: an expected table or option is absent; idea: an improvement; docs: unclear guidance; praise: it worked well; other |
| selection | string | – | The selection or query involved, as JSON or the SDMX key |
| shareWithAbs | boolean | – | Only true if the person agreed this may be passed on to ABS, contact address included |
| summary | string | – | One line, in the person's own words |
| table | string | – | The ABS table id involved, e.g. CPI |
| tool | string | – | The tool involved, e.g. get_data |
| Name | Type | Req | Description |
|---|---|---|---|
| draft | object | yes | – |
| next | string | yes | – |
No examples provided.
get_data Get data ~213
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 | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| availabilityUrl | string | yes | – |
| fullDataUrl | string | yes | – |
| key | string | yes | The resolved selection as an SDMX key |
| periodRange | object | yes | – |
| provenance | object | yes | – |
| rows | array | yes | – |
| rowsReturned | integer | yes | – |
| seriesMatched | integer | yes | – |
| table | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
search Search the catalogue by writing code ~368
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 | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript. `catalogue` is in scope. Must return a value. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| logs | array | yes | – |
| ok | boolean | yes | – |
| result | – | – | – |
| truncated | boolean | – | – |
No examples provided.
search_options Search a dimension's options ~76
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 | Type | Req | Description |
|---|---|---|---|
| dimension | string | yes | – |
| limit | integer | – | – |
| query | string | yes | Match against option codes and labels |
| table | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | – |
| provenance | object | yes | – |
| total | integer | yes | – |
No examples provided.
search_tables Search ABS tables ~204
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 has data. When the person describes a situation rather than a dataset, search for each thing it depends on (prices, wages, rents, population...). Start here, then describe_table.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| provenance | object | yes | – |
| results | array | yes | – |
| total | integer | yes | – |
No examples provided.
submit_feedback Send feedback to the maintainers ~391
Send feedback about this ABS connector (or a report about ABS's own data) to its maintainers. Only call this after the person has seen the exact text and said to send it — prefer feedback_form, which lets them edit it first. Use about='abs' for wrong figures or broken behaviour in ABS's own data or API; set shareWithAbs only if the person agreed it may be passed on to ABS. Never include personal information about anyone, and include a contact email only if the person gave one for a reply. Returns a reference like FB-7Q2K9C to give the person.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | connector: this connector or its site; abs: ABS's own data or API (so it can be passed on to ABS) |
| assistant | string | – | The AI tool in use, e.g. Claude, ChatGPT, Copilot |
| contact | string | – | Only if the person chose to give an email address for a reply. Never guess or fill one in. |
| details | string | – | What happened and what was expected. No personal information about anyone. |
| error | string | – | The error reason or message returned, if any |
| kind | string | yes | bug: something broke; data: a figure or label looks wrong; missing: an expected table or option is absent; idea: an improvement; docs: unclear guidance; praise: it worked well; other |
| selection | string | – | The selection or query involved, as JSON or the SDMX key |
| shareWithAbs | boolean | – | Only true if the person agreed this may be passed on to ABS, contact address included |
| summary | string | yes | One line, in the person's own words |
| table | string | – | The ABS table id involved, e.g. CPI |
| tool | string | – | The tool involved, e.g. get_data |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Reference for this submission, e.g. FB-7Q2K9C |
| message | string | yes | – |
| receivedAt | string | yes | – |
No examples provided.
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.
remote · abs-data-front-door.aicolab.workers.dev
claude mcp add --transport http samjb123-abs-data 'https://abs-data-front-door.aicolab.workers.dev/mcp'
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 80 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 8 tools: search_tables, describe_table, search_options, get_data, search, and 3 more. Their descriptions and schemas cost roughly 2,269 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ABS Data (observed) MCP server?
VerifyMCP ran 12 checks on ABS Data (observed), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ABS Data (observed): HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.