Ext Ops Panel
Open dashboard
Comparison

Xero vs BuilderVet — NSW builder licence & risk history

Xero is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). 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-13. 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
MarketplaceXeroBuilderVet — NSW builder licence & risk history
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 086
Stars (GitHub): 11 186
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

Xero vs BuilderVet — NSW builder licence & risk history
FactXeroBuilderVet — NSW builder licence & risk history
Marketplaces that list it11
Stars (GitHub) (differs)11 186No figure on GitHub
Forks (GitHub) (differs)1 086No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@xeroapi/xero-mcp-server)Remote server (mcp.buildervet.au)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.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 checknot checked yet

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

Xero

In its own words, on Cursor: cursor/plugins:

Read and write invoices, contacts, reports, and payroll.

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

Xero

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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.

Tools each declares

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

Settings each asks for

The marketplaces of BuilderVet — NSW builder licence & risk history publish no settings it asks for, so we do not compare settings.

What it can do: Xero · What it can do: BuilderVet — NSW builder licence & risk history · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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