Use autozoo from your agent

One MCP server for Australian vehicle recalls. No key, no signup, no per-call billing. The same answers the website gives, in the shape an agent can act on.

https://autozoo.com.au/mcp

What agents can do

/agent-capability.json is the machine version. “Planned” means it does not exist; do not attempt it.

Reading a result

Every match carries a basis, and the difference matters:

• vin_list — the regulator named this VIN in a published list.
• vin_range_exact — inside bounds the notice prints in full.
• vin_range_envelope — inside a production range whose check digit, and sometimes model year, is not published. In scope, not confirmed.

no_record means this corpus could not find the VIN. Some campaigns publish no VIN list, so never tell a person their car has no recalls.

Consent

Reads need no consent and no key. The one write — registering a VIN for monitoring — will require the owner's email and an explicit consent assertion, because it creates an ongoing relationship with a person:

{
  "vin": "6K9CAVECXSM804000",
  "email": "owner@example.com",
  "customer_consent": { "confirmed": true, "basis": "customer_requested_recall_watch" },
  "idempotency_key": "agent-session-12345"
}

Retries reuse the idempotency key. No payment is taken here, and no repair is booked here.

Private surfaces

Do not crawl, submit to, or automate:

• /v1/admin/* — operator routes, token-gated
• /v1/probe/url — diagnostics
• /w/<token> — personal watch pages
• /v1/watchlists — bearer token required

Discovery

• /llms.txt and /.well-known/llms.txt
• /agent-capability.json
• /openapi.json
• /agents/skill.md
• POST /mcp — Streamable HTTP, no auth