nz-yard-stock
Registry code: f37343542a027abf
Live used-car stock on named NZ dealer yards. Search make, model, price, city. Not Trade Me.
from a public catalogue that lists it, not from the operator
- endpoint
- https://stock.yardstock.nz/mcp
- door code
- 2af0a297ccb25af6
- protocol
- https://modelcontextprotocol.io/specification/basic/transports#streamable-http ·1.0
- authentication
- bearer
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is nz-yard-stock live?
- Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
- Is nz-yard-stock free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does nz-yard-stock have?
- 3 tools: Search live dealer stock, Report dealer-yard coverage, Resolve one listing.
- Is nz-yard-stock safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search used cars at nz dealer yards
- get a used car listing
- list covered dealers
- takes → gives
- text, data → data
- tools
- 1 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search-stock auth-required never probed
Find live used vehicles on covered NZ dealer yards by make, model, year range, price range in NZD, city or suburb, and fuel type. Results are sorted by price ascending and link to the dealer's own listing page. Anonymous callers receive at most 5 results per call and no VIN or plate.
coverage reads auth-required never probed
List the New Zealand dealer groups currently in the index with their live listing counts and cities, plus what is explicitly not included. Call this before making any claim about the wider NZ market.
get-listing auth-required never probed
Fetch a single vehicle listing by its exact source_url, including VIN and plate where the yard published them and the caller is using an API key. Unknown URLs return not_found, which usually means the vehicle has sold.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf37343542a027abf.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f37343542a027abf/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f37343542a027abf?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.