Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BuilderVet: NSW and QLD builder licence and risk history

REMOTE · MCP.BUILDERVET.AU

BuilderVet: is this NSW or QLD builder licensed, insolvent or disciplined? 290k+ official records.

0 this week 77 Trust /100

Last scanned (20 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Security

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 628 tokens (~125/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 Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 21 Oct 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
  • 20 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_builders” rewrote its description, which is the text the model reads security
  • 10 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_builder_risk” rewrote its description, which is the text the model reads security
    • Tool “get_builder_timeline” rewrote its description, which is the text the model reads security
    • Tool “search_builders” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 50% ▼ functional
    • Schema quality: 262 → 121 ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “get_builder_changes” functional
    • New tool “get_builder_coverage” functional
    • “get_builder_risk” reworded the description of “slug” cosmetic
    • “get_builder_timeline” reworded the description of “slug” cosmetic
    • “search_builders” reworded the description of “postcode” cosmetic
    • “search_builders” reworded the description of “query” cosmetic
  • 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
  • 6 Sept 26 0
    • Tool “get_builder_risk” rewrote its description, which is the text the model reads security
    • Tool “get_builder_timeline” rewrote its description, which is the text the model reads security
  • 26 Aug 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 Aug 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 4 Nov 2026 · Probed https://mcp.buildervet.au/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=buildervet.au CN=WE1,O=Google Trust Services,C=US 10 Sept 2026 9 Dec 2026 ECDSA 256 ECDSA-SHA256 d3f84265544676cf131e4aad902281e9
SANs: buildervet.au, mcp.buildervet.au, *.mcp.buildervet.au
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 mcp.buildervet.au. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
au. present 26642 8 Verified
buildervet.au. absent 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
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.buildervet.au/ Verified 200
http (plaintext) http://mcp.buildervet.au/ Served over HTTP 200
MCP tools · 5 exposed · ~383 tokens

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 →

Tool Tokens
get_builder_changes ~97

Page the public dated event timeline, newest event date first. This is recorded history, not private monitoring notifications or a since-last-run feed. Default 25, maximum 100 events. Pass nextCursor unchanged; restart without a cursor if the timeline changed. Public API response is capped at 500 rows.

NameTypeReqDescription
cursorstring––
limitinteger––
slugstringyesBuilder slug from search_builders.

No output schema declared.

No examples provided.

get_builder_coverage ~74

Read public per-source check states, result details, last attempt/success dates, next due dates and source URLs. This reads recorded state; it does not rerun checks or enable monitoring. Unchecked, stale and unavailable are gaps, not clear results.

NameTypeReqDescription
slugstringyesBuilder slug from search_builders.

No output schema declared.

No examples provided.

get_builder_risk ~68

Read one builder's public identity, licences, company status and stored source flags. Facts only: flags are not a safety rating, and missing records are not a clearance. Use get_builder_coverage for check dates and gaps.

NameTypeReqDescription
slugstringyesBuilder slug from search_builders.

No output schema declared.

No examples provided.

get_builder_timeline ~73

Read the first 50 public timeline events, newest event date first. Each event retains its source, occurrence/detection dates and archive flag. Use get_builder_changes to page further; the public API holds at most 500 timeline rows in this response.

NameTypeReqDescription
slugstringyesBuilder slug from search_builders.

No output schema declared.

No examples provided.

search_builders ~71

Find NSW and Queensland builders by name, ABN, ACN or licence number (NSW or QBCC), optionally within a postcode. Resolve the legal entity before reading its record. Try the legal company name if a trading name misses.

NameTypeReqDescription
postcodestring––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the BuilderVet: NSW and QLD builder licence and risk history MCP server?

BuilderVet: NSW and QLD builder licence and risk history is a hosted endpoint at https://mcp.buildervet.au/, 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 · mcp.buildervet.au

# add to Claude Code
claude mcp add --transport http jackfieldman-buildercheck 'https://mcp.buildervet.au/'
Common questions

What is the BuilderVet: NSW and QLD builder licence and risk history MCP server?

BuilderVet: NSW and QLD builder licence and risk history is an MCP server listed in the public MCP registry as io.github.jackfieldman/buildercheck. BuilderVet: is this NSW or QLD builder licensed, insolvent or disciplined? 290k+ official records. This page covers its hosted endpoint (https://mcp.buildervet.au/).

Is the BuilderVet: NSW and QLD builder licence and risk history MCP server safe to use?

BuilderVet: NSW and QLD builder licence and risk history scores 77 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 BuilderVet: NSW and QLD builder licence and risk history MCP server expose?

BuilderVet: NSW and QLD builder licence and risk history exposes 5 tools: search_builders, get_builder_risk, get_builder_timeline, get_builder_coverage, get_builder_changes. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.

Does the BuilderVet: NSW and QLD builder licence and risk history MCP server require authentication?

No. We connected to BuilderVet: NSW and QLD builder licence and risk history without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BuilderVet: NSW and QLD builder licence and risk history MCP server still maintained?

BuilderVet: NSW and QLD builder licence and risk history is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.