io.ausdata/asic-mcp
PYPI · ASIC-MCP
Query ASIC registers in plain English — advisers, licensees, banned persons, liquidators.
Available components
Last scanned (3 hours ago)
Scores higher than 90% of PyPI servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to Bigred97/asic-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 80 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1530 tokens (~306/item across 5 items; 5 tools + 0 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 23 Oct 26 −5
- Source repository: pass → fail ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 99 to 100.
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed pypi/asic-mcp@0.6.21
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Bigred97/asic-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Bigred97/asic-mcp/.github/workflows/release.yml@refs/tags/v0.6.21 |
| Rekor log index | 2472805779 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fd4996efe78e6c545ff0944b765ab6b8d3f9a7fbc7aec814ea473b09117cf16f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_dataset ~145
Describe a dataset's filterable dimensions, returnable measures, and source. Use this before calling get_data on a new dataset — it tells you the valid filter keys ('current_status', 'state', 'business_name'), the valid filter values ('current', 'ceased', 'nsw', 'vic'), and the source URL. Returns: DatasetDetail with id, name, description, period_coverage, list of dimensions, list of measures, source_url, and download_url.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Curated dataset ID. Use the search endpoint or search tool to discover, or the list-curated endpoint/tool to enumerate. Case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| dimensions | array | – | – |
| download_url | – | – | – |
| id | string | yes | – |
| is_curated | boolean | yes | – |
| measures | array | – | – |
| name | string | yes | – |
| period_coverage | – | – | – |
| source_url | string | yes | – |
| update_frequency | – | – | – |
No examples provided.
get_data ~573
Query a curated ASIC register dataset and return matching rows. Examples: # All currently registered financial advisers in NSW resp = await get_data( "ASIC_FINANCIAL_ADVISERS", filters={"current_status": "current", "state": "nsw"}, ) # AFS licensees whose legal name contains "Macquarie" resp = await get_data( "ASIC_AFS_LICENSEE", filters={"licensee_name": "Macquarie"}, ) # Persons banned or disqualified after 2024 resp = await get_data( "ASIC_BANNED_PERSONS", start_period="2024-01-01", ) # Full authorisation text for one AFS licensee resp = await get_data( "ASIC_AFS_LICENSEE", filters={"licensee_name": "Macquarie Bank Limited"}, include_full_authorisation=True, ) Returns: DataResponse with records (or csv), unit, period bounds, row_count, source URL, and CC-BY 3.0 AU attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Curated dataset ID. Use the search or list-curated endpoint/tool to discover. |
| end_period | – | – | Inclusive end date. Same format as start_period. |
| filters | – | – | Dimension filters. Keys are plain-English aliases from the dataset's describe_dataset response. Values are matched against the source data; pass a list to OR across values. Examples: {'current_status… |
| format | string | – | Response shape. 'records' (default): flat list of observations. 'series': grouped by measure. 'csv': pandas CSV string in `csv` field. |
| include_full_authorisation | boolean | – | ASIC_AFS_LICENSEE only. The `authorisation` field carries 2-3 KB of license boilerplate per record (which financial services and products the licensee may deal in). To keep responses under the portfo… |
| start_period | – | – | Inclusive start date for time-bounded register fields (date of registration, date banned, etc.). Format: 'YYYY', 'YYYY-MM', or 'YYYY-MM-DD'. Bare int years like 2020 are coerced to '2020' automatical… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| csv | – | – | – |
| dataset_id | string | yes | – |
| dataset_name | string | yes | – |
| period | object | – | – |
| query | object | – | – |
| records | array | – | – |
| retrieved_at | string | yes | – |
| row_count | integer | – | – |
| server_version | string | – | – |
| source | string | – | – |
| source_url | string | yes | – |
| stale | boolean | – | – |
| stale_reason | – | – | – |
| truncated_at | – | – | – |
| unit | – | – | – |
No examples provided.
latest ~496
Return the most recent observation(s) per measure for a dataset. For register data, "latest" is the current weekly/monthly snapshot capped at `limit` rows (default 50). For time-bounded fields (date_banned, date_ceased), latest returns the most recent matching record per entity. Pass `filters` to drill into one entity (no truncation hits) or raise `limit` to request more rows. Examples: # Current registered status for one adviser (precise filter, no truncation) resp = await latest( "ASIC_FINANCIAL_ADVISERS", filters={"adviser_number": "1234567"}, ) # First 50 most-recent banned persons (truncated; full count in resp.truncated_at) resp = await latest("ASIC_BANNED_PERSONS") # Get 500 rows in one go (still capped, but bigger window) resp = await latest("ASIC_AFS_LICENSEE", limit=500) # Full authorisation text for one AFS licensee resp = await latest( "ASIC_AFS_LICENSEE", filters={"licensee_name": "Macquarie Bank Limited"}, include_full_authorisation=True, )
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Curated dataset ID. |
| filters | – | – | Same filter shape as get_data. Useful for narrowing to one entity. MCP clients that cannot send a native object may pass this as a JSON-encoded string instead, e.g. '{"adviser_number": "1234567"}'. |
| include_full_authorisation | boolean | – | ASIC_AFS_LICENSEE only. The `authorisation` field carries 2-3 KB of license boilerplate per record. To stay under the portfolio's 10k-token target, that field is truncated to ~200 chars by default. P… |
| limit | integer | – | Maximum rows to return. ASIC registers can be huge — ASIC_AFS_AUTH_REP alone has ~360,000 rows. Without a cap the response blows an agent's context window. Pass filters to narrow the search; raise `l… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| csv | – | – | – |
| dataset_id | string | yes | – |
| dataset_name | string | yes | – |
| period | object | – | – |
| query | object | – | – |
| records | array | – | – |
| retrieved_at | string | yes | – |
| row_count | integer | – | – |
| server_version | string | – | – |
| source | string | – | – |
| source_url | string | yes | – |
| stale | boolean | – | – |
| stale_reason | – | – | – |
| truncated_at | – | – | – |
| unit | – | – | – |
No examples provided.
list_curated ~64
List every curated dataset ID in this version of asic-mcp. These are the datasets where get_data accepts plain-English filter keys and returns aliased, well-typed columns. Each ID is documented via describe_dataset. Returns: Sorted list of dataset IDs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_datasets ~252
Fuzzy-search the curated ASIC dataset catalogue. The curated set of hand-curated ASIC registers covers Financial Advisers, AFS Licensees, AFS Authorised Representatives, Credit Licensees, Credit Representatives, Banned and Disqualified Persons, Banned and Disqualified Organisations, Registered Liquidators, Registered Company Auditors, SMSF Auditors, Companies, Business Names, and Short Positions. Call `list_curated()` to get the live list rather than assuming a fixed count — the registry grows over time. Examples: # Find the financial advisers register results = await search_datasets("financial adviser") # → [{id: 'ASIC_FINANCIAL_ADVISERS', name: 'Financial Advisers Register', ...}] # Discover what's available on enforcement-related lists results = await search_datasets("banned") Returns: List of DatasetSummary (id, name, description, update_frequency, is_curated), ranked by relevance.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return, ranked by relevance. |
| query | string | yes | Free-text search query. Matches against dataset IDs, names, descriptions, and curated search keywords. Case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the io.ausdata/asic-mcp server?
io.ausdata/asic-mcp runs locally as a PyPI package, launched with uvx asic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · asic-mcp
claude mcp add io-ausdata-asic-mcp -- uvx asic-mcp
What is the io.ausdata/asic-mcp server?
io.ausdata/asic-mcp is listed in the public MCP registry as io.ausdata/asic-mcp. Query ASIC registers in plain English, advisers, licensees, banned persons, liquidators. This page covers its PyPI package (asic-mcp).
Is the io.ausdata/asic-mcp server safe to use?
io.ausdata/asic-mcp scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 io.ausdata/asic-mcp server expose?
io.ausdata/asic-mcp exposes 5 tools: search_datasets, describe_dataset, get_data, latest, list_curated. Their descriptions and schemas cost roughly 1,530 tokens of context every time the server is loaded.
Is the io.ausdata/asic-mcp server still maintained?
io.ausdata/asic-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.ausdata/asic-mcp server under?
io.ausdata/asic-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.