YardStock NZ Vehicle Listings MCP server
nz.yardstock/nz-car-listingsyardstock.nzstreamable-httpv1.0.0Scanned
Live used-car stock on named NZ dealer yards. Search make, model, price, city. Not Trade Me.
4 tools: 1 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the YardStock NZ Vehicle Listings MCP server can do
The YardStock NZ Vehicle Listings MCP server is published by yardstock.nz, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: coverage), but cannot delete data. 3 tools only read.
1 tool reads private data (search_stock); 1 tool brings in text other people can write (get_listing).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
coverageWho is in this NZ dealer-yard stock product.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Who is in this NZ dealer-yard stock product. Call first.
Only reads 3Show 3 read-only tools
get_listingFetch one listing by its source_url.Reads text others writeNo findings
Why it is in this group
- The name "get_listing" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch one listing by its source_url.
search_stockSearch live used cars on ingested NZ dealer yards, with the same filters, ranking and notes as the YardStock search page.Reads private dataNo findings
Why it is in this group
- The name "search_stock" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "note": it reads notes.
Description, as the server wrote it Search live used cars on ingested NZ dealer yards, with the same filters, ranking and notes as the YardStock search page. Exact matches only. Returns `total` (every exact match) and up to `limit` of them. Not Trade Me.
search_textThe same search from one plain sentence, read the way the search page reads it: "diesel 4wd under 40000 in Auckland".No findings
Why it is in this group
- The name "search_text" says "search": a word for reading.
Description, as the server wrote it The same search from one plain sentence, read the way the search page reads it: "diesel 4wd under 40000 in Auckland". Echoes what it read (`filters`, `phrase`) and what it could not (`unparsed`).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://stock.yardstock.nz/mcp: tools/list returned 4 tools to an anonymous client, including coverage (write)
Posture changes
- Nov 20, 2026
- Protocol version: 2024-11-05 to 2025-06-18
- RFC 9728 protected resource metadata: https://stock.yardstock.nz/.well-known/oauth-protected-resource to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18; RFC 9728 protected resource metadata: https://stock.yardstock.nz/.well-known/oauth-protected-resource -> none.View diff
- Protocol version: 2024-11-05 to 2025-06-18
- RFC 9728 protected resource metadata: https://stock.yardstock.nz/.well-known/oauth-protected-resource to none
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:search_textOnly reads
- Changed:search_stockOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http nz-car-listings https://stock.yardstock.nz/mcpclaude mcp add --transport http nz-car-listings https://stock.yardstock.nz/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nz-car-listings__search_stock",
"mcp__nz-car-listings__search_text",
"mcp__nz-car-listings__get_listing"
],
"ask": [
"mcp__nz-car-listings__coverage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nz-car-listings. Review it before you use it.
Capability tags behind 2 rules
- mcp__nz-car-listings__search_stock private-data
- mcp__nz-car-listings__get_listing untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/nz.yardstock/nz-car-listings/verify?hash=93d39777b528c16f48c2fcf2b3251d30a0e9c59453905fbdc10feda69667d337" | jq -e '.changed == false'Pinned hash 93d39777b528, from Nov 18, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/nz.yardstock/nz-car-listings/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/nz.yardstock/nz-car-listings)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
YardStock NZ Vehicle Listings MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the YardStock NZ Vehicle Listings MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the YardStock NZ Vehicle Listings MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the YardStock NZ Vehicle Listings MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the YardStock NZ Vehicle Listings MCP server have?
- 4 tools: 1 write, 3 read. coverage, search_stock, search_text and get_listing.
Does the YardStock NZ Vehicle Listings MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the YardStock NZ Vehicle Listings MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the YardStock NZ Vehicle Listings MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.