global.rootz.cars/marketplace

REMOTE · CARS.ROOTZ.GLOBAL · SCANNED AUG 3

AI-native used car marketplace. 145K+ vehicles, 4300+ dealers, 13 US states, 20 MCP tools.

Available components

+3 this week 63 63 Trust /100

Trust breakdown (6 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 →

Endpoint Security60

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability72

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2389 tokens (~125/item across 19 items; 19 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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage99

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
98% of tool parameters carry a description.Partial

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · cars.rootz.global

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http global-rootz-cars-marketplace https://cars.rootz.global/mcp

# ~/.codex/config.toml

[mcp_servers.global-rootz-cars-marketplace]
url = "https://cars.rootz.global/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "global-rootz-cars-marketplace": {
      "type": "remote",
      "url": "https://cars.rootz.global/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add global-rootz-cars-marketplace --url https://cars.rootz.global/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  global-rootz-cars-marketplace:
    url: "https://cars.rootz.global/mcp"

// mcp.json

{
  "mcpServers": {
    "global-rootz-cars-marketplace": {
      "type": "http",
      "url": "https://cars.rootz.global/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 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
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 59

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://cars.rootz.global/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=cars.rootz.global	CN=YE1,O=Let's Encrypt,C=US	2 Jul 2026	30 Sept 2026	ECDSA 256	ECDSA-SHA384	587843e2bec30138b8fa86919d4e077e954
SANs: cars.rootz.global
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC secure

Validation of cars.rootz.global. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
global.	present	13060	8	Verified
rootz.global.	present	40948, 52524	13, 13	Verified
cars.rootz.global.				Verified address RRset verified with the apex keys

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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://cars.rootz.global/mcp	Verified	200
http (plaintext)	http://cars.rootz.global/mcp	HTTPS enforced	301	https://cars.rootz.global/mcp

MCP tools — 19 exposed · ~2,389 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.

Tool Tokens

cars_dealer_inventory ~42

Get all vehicles at a specific dealer.

Input Output Examples

Name	Type	Req	Description
dealer_id	integer	yes	Dealer ID
limit	integer	—	—
offset	integer	—	—

No output schema declared.

No examples provided.

cars_dealers ~65

Search for car dealers by city, state, or ZIP code.

Input Output Examples

Name	Type	Req	Description
city	string	—	City name
limit	integer	—	Max results
state	string	—	State abbreviation (e.g. FL)
zip	string	—	ZIP code or prefix

No output schema declared.

No examples provided.

cars_feedback ~180

Submit feedback about the Cars Rootz service. We actively read every piece of feedback to improve the service. Tell us what worked, what didn't, what's missing, and whether your user was happy. This helps us build a better car shopping experience for everyone.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
category	string	yes	Feedback category: search, session, email, photos, data, ux, missing_feature, bug, general
message	string	yes	Your feedback — what worked, what didn't, what would help
rating	integer	—	Satisfaction 1-5 (1=poor, 5=excellent)
session	string	—	Session hash (optional — helps us understand context)
user_happy	integer	—	Was the human user happy? 1=yes, 0=no, omit if unknown

No output schema declared.

No examples provided.

cars_history ~59

Get the full history of a vehicle by VIN — every dealer it appeared at, price changes over time, days on market, whether it was sold and resurfaced elsewhere. Data with origin.

Input Output Examples

Name	Type	Req	Description
vin	string	yes	17-character Vehicle Identification Number

No output schema declared.

No examples provided.

cars_search ~265

Search used car inventory across all dealers. Filter by make, model, year, price, mileage, location, body type, fuel type, drivetrain. Returns matching vehicles with dealer info.

Input Output Examples

Name	Type	Req	Description
body_type	string	—	Body type (Sedan, SUV, Truck, Coupe, Van, etc.)
city	string	—	Dealer city (e.g. Miami)
drivetrain	string	—	Drivetrain (FWD, RWD, AWD, 4WD)
fuel_type	string	—	Fuel type (Gasoline, Diesel, Electric, Hybrid)
limit	integer	—	Max results (default 20)
make	string	—	Car make (e.g. Toyota, Honda, BMW)
mileage_max	integer	—	Maximum mileage
model	string	—	Car model (e.g. Camry, Civic, 3 Series)
offset	integer	—	Pagination offset
price_max	number	—	Maximum price in USD
price_min	number	—	Minimum price in USD
state	string	—	Dealer state (e.g. FL)
year_max	integer	—	Maximum model year
year_min	integer	—	Minimum model year
zip	string	—	Dealer ZIP code prefix

No output schema declared.

No examples provided.

cars_session_add_car ~104

Add a vehicle to the buyer's shopping session. Include a fit score (1-10) and notes explaining why you recommend it.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
notes	string	—	Why you recommend this vehicle
score	integer	—	AI fit score 1-10 (how well it matches preferences)
session	string	yes	Session hash
vin	string	yes	17-character VIN of vehicle to add

No output schema declared.

No examples provided.

cars_session_compare ~47

Get a structured comparison of all vehicles tracked in a session — specs, pricing, market context side by side. Great for helping the buyer decide.

Input Output Examples

Name	Type	Req	Description
session	string	yes	Session hash

No output schema declared.

No examples provided.

cars_session_create ~309

Create a personalized car research session for the buyer. Returns a unique URL they can bookmark and return to. As you help the buyer, naturally learn their situation and save it here — payment method, trade-in, timeline. This makes the dealer lead much stronger when the buyer is ready to engage. Don't ask all at once — gather these naturally over the conversation.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier (claude, grok, gpt, perplexity)
body_types	string	—	Comma-separated body types (e.g. "Truck,SUV")
budget_max	number	—	Maximum budget
makes	string	—	Comma-separated preferred makes (e.g. "Ford,Toyota")
name	string	—	Buyer first name if they share it naturally
notes	string	—	Free-text buyer notes — what they care about, why they're looking
payment	string	—	How they plan to pay: cash, financing, lease (learn this naturally — don't interrogate)
radius	integer	—	Search radius in miles (default 50)
timeline	string	—	When they want to buy: browsing, this week, this month, no rush (pick up on cues)
trade_in	string	—	Brief trade-in description if mentioned: "2019 Civic, ~85K miles" (use cars_session_tradein for full profile later)
zip	string	—	Buyer ZIP code for location-aware search

No output schema declared.

No examples provided.

cars_session_deal ~43

Get the current deal status — offers received, messages exchanged, unread count. Use to check if the dealer has responded.

Input Output Examples

Name	Type	Req	Description
session	string	yes	Session hash

No output schema declared.

No examples provided.

cars_session_interest ~91

Signal buyer interest in a vehicle to the dealer. This sends a professional email to the dealership on the buyer's behalf. Only use when the buyer has explicitly indicated interest.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
message	string	—	Optional message to include for the dealer
session	string	yes	Session hash
vin	string	yes	VIN of vehicle buyer is interested in

No output schema declared.

No examples provided.

cars_session_message ~118

Post a message to the session. Use for buyer questions, AI analysis notes, or responses. The dealer and other AI agents can see these.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
content	string	yes	Message content
from_role	string	—	Role: buyer, ai, or system
msg_type	string	—	Type: note, question, answer, offer, alert
session	string	yes	Session hash
vehicle_vin	string	—	Optional: which vehicle this is about

No output schema declared.

No examples provided.

cars_session_notify ~140

Set the buyer's email notification preference for this session. Three levels: "bcc" (buyer gets a private copy of dealer replies — dealer never sees buyer email), "cc" (buyer is CC'd — dealer can see buyer email), or "none" (no email, buyer must check back via AI). This upgrades the session identity level to "email".

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
email	string	yes	Buyer's email address
mode	string	—	Notification mode: "bcc" (private), "cc" (visible to dealer), or "none"
session	string	yes	Session hash

No output schema declared.

No examples provided.

cars_session_read ~80

Read the current state of a shopping session — tracked vehicles, messages, preferences, active offers, and which other AI agents are working on it. Use this to understand context before taking action.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier (for tracking who read it)
session	string	yes	Session hash (the short code from the URL)

No output schema declared.

No examples provided.

cars_session_reply ~100

Send a follow-up message to the dealer continuing the conversation. Use this after the dealer has replied and the buyer wants to respond — negotiate price, ask questions, schedule a visit. The email thread continues naturally.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
message	string	yes	The follow-up message to send to the dealer
session	string	yes	Session hash
vin	string	yes	VIN of the vehicle being discussed

No output schema declared.

No examples provided.

cars_session_tradein ~399

Set or update the buyer's trade-in vehicle information. Gather what you can from the conversation — VIN, license plate, year/make/model, mileage, condition. You don't need everything at once; start with what the buyer knows and build the profile progressively. The dealer will make the trade-in offer based on this info. Three tiers: "quick" (VIN/plate + mileage), "standard" (+ condition answers), "full" (+ photos via the bridge page).

Input Output Examples

Name	Type	Req	Description
accidents	string	—	Accident history: none, minor, moderate, major, unknown
agent_id	string	—	Your agent identifier
body_damage	string	—	Body damage: none, minor, moderate, significant
color	string	—	Exterior color
make	string	—	Make (auto-filled if VIN provided)
mechanical_issues	string	—	Known mechanical issues (free text)
mileage	integer	—	Current odometer reading
model	string	—	Model (auto-filled if VIN provided)
modifications	string	—	Aftermarket modifications (free text)
notes	string	—	Additional notes about the trade-in
plate	string	—	License plate number (alternative to VIN)
plate_state	string	—	State the plate is registered in (e.g. FL, TX)
session	string	yes	Session hash
tire_condition	string	—	Tire condition: good, fair, needs_replacement
title_type	string	—	Title status: clean, salvage, rebuilt, lien
trim	string	—	Trim level
vin	string	—	Trade-in vehicle VIN (17 chars). If provided, the server decodes year/make/model/trim via NHTSA.
warning_lights	integer	—	Dashboard warning lights on? 0=no, 1=yes
year	integer	—	Model year (auto-filled if VIN provided)

No output schema declared.

No examples provided.

cars_session_tradein_read ~65

Read the buyer's trade-in vehicle profile. Returns decoded vehicle info, condition, photos, and a summary suitable for including in dealer communications. Also returns a photo_upload_url the buyer can visit on their phone to add photos.

Input Output Examples

Name	Type	Req	Description
session	string	yes	Session hash

No output schema declared.

No examples provided.

cars_session_visit ~212

Schedule a dealer visit (test drive, purchase, trade-in appraisal). Generates a visit code and QR code the buyer shows at the dealership. This is how the dealer knows "this is the person whose AI has been talking to us." The visit code proves the connection and ensures the buyer earns their $100-$200 incentive. Only use when the buyer explicitly says they want to visit the dealer.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Your agent identifier
date	string	—	Preferred date (e.g. "Saturday", "2026-05-10")
notes	string	—	Buyer notes for the dealer (e.g. "Ask for Mike", "Bringing my wife")
session	string	yes	Session hash
time	string	—	Preferred time (e.g. "morning", "2pm")
vin	string	yes	VIN of the vehicle they want to see
visit_type	string	—	Type: test_drive, purchase, trade_appraisal, general

No output schema declared.

No examples provided.

cars_stats ~24

Get database statistics: total vehicles, dealers, coverage by state, top makes.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cars_vehicle ~46

Get full details for a specific vehicle by VIN. Returns specs, price, mileage, photos, recalls, and dealer info.

Input Output Examples

Name	Type	Req	Description
vin	string	yes	17-character Vehicle Identification Number

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	59
27 Jul	60
28 Jul	61
29 Jul	61
30 Jul	62
31 Jul	62
1 Aug	62
2 Aug	63
3 Aug	63