Ext Ops Panel
Open dashboard
Comparison

io.ausdata/asic-mcp vs BuilderVet — NSW builder licence & risk history

io.ausdata/asic-mcp is an MCP server published by ausdata.io. Marketplaces we read that list it: 1 (Official MCP Registry). BuilderVet — NSW builder licence & risk history is an MCP server published by jackfieldman. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.ausdata/asic-mcpBuilderVet — NSW builder licence & risk history
Official MCP Registry Listed
Version: 0.6.21
Downloads/month (PyPI): 505
Downloads/week (PyPI): 116
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.3
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.ausdata/asic-mcp vs BuilderVet — NSW builder licence & risk history
Factio.ausdata/asic-mcpBuilderVet — NSW builder licence & risk history
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (asic-mcp)Remote server (mcp.buildervet.au)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/bigred97/asic-mcpgithub.com/jackfieldman/buildervet
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.ausdata/asic-mcp

In its own words, on Official MCP Registry:

Query ASIC registers in plain English — advisers, licensees, banned persons, liquidators.

BuilderVet — NSW builder licence & risk history

In its own words, on Official MCP Registry:

Is this NSW builder licensed, insolvent or disciplined? 178k+ licences from official registers.

How to run each

io.ausdata/asic-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio asic-mcp -- uvx asic-mcp

BuilderVet — NSW builder licence & risk history As a remote MCP server

Claude Code
claude mcp add --transport http buildercheck https://mcp.buildervet.au/

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only BuilderVet — NSW builder licence & risk history has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.ausdata/asic-mcp · What it can do: BuilderVet — NSW builder licence & risk history · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built