Everroad: Utah car dealer facts
REMOTE · EVERROAD.ORG
Utah franchise car dealer facts with sources: hours, weekend service, doc fees, services.
Available components
Last scanned (7 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 997 tokens (~142/item across 7 items; 7 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 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.
- 2 Nov 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.
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
First indexed and scored.
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 5 Nov 2026 · Probed https://everroad.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=everroad.org | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 31b0712174991e9c0e38209752778196 |
| SANs: everroad.org, www.everroad.org, *.www.everroad.org | ||||||
| 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 everroad.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| everroad.org. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; img-src 'self' data: https://i.ytimg.com https://*.cdninstagram.com https://*.fbcdn.net https://upload.wikimedia.org https://live.staticflickr.com; style-src 'self' 'unsafe-inline'; font-src 'self'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://everroad.org/mcp | Verified | 200 | |
| http (plaintext) | http://everroad.org/mcp | Inconclusive | 405 |
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 →
compare_dealers Compare dealers ~82
Facts for 2 to 5 dealers side by side, in the order given: hours, weekend sales and service, posted doc fee, service and buying options, and each Everroad Score with its basis. A fact one dealer has not stated shows as not stated. It lines the facts up; it names no winner.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | – |
No output schema declared.
No examples provided.
dealer_facts Dealer facts ~81
Every fact on record for one dealer (by slug from find_dealers, or by name): its Everroad Score (0 to 100) with the category breakdown and a link to every metric, hours by department, weekend service, posted doc fee, service options, with the source URL and checked date of each fact.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
dealer_score Dealer score ~105
One dealer's Everroad Score (0 to 100): the number, band and formula version, each category's points, measured-weight coverage (how much of the score rests on the store's own data), every measured metric with its source, and the metrics the dealer controls through its own website that are not on record (for example a posted doc fee or hours in structured data). Slug from find_dealers, or the dealer's name.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
fee_law Utah dealer fee and weekend law ~43
What Utah law says about the dealer documentary (doc) fee and the Saturday/Sunday selling rule, with the explainer page URLs and the date the sources were checked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_dealers Find dealers ~153
List franchise car dealers in Utah, optionally by county market (e.g. "salt-lake-county" or "Davis County"), make (e.g. "Toyota"), city (e.g. "Murray") and service option (saturday-service, sunday-service, collision-center, buy-online, express-service, loaner-cars, spanish-speaking). Ordered by county market, then distance from that county's reference point (downtown Salt Lake City for Salt Lake County). Returns each dealer page URL and when it was last checked.
| Name | Type | Req | Description |
|---|---|---|---|
| attribute | string | – | – |
| city | string | – | – |
| limit | integer | – | – |
| make | string | – | – |
| market | string | – | – |
No output schema declared.
No examples provided.
report Report ~43
The numbers of a published report, with coverage and method link. Slug: utah-weekend-dealer-access (the Weekend Access Report).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | – |
No output schema declared.
No examples provided.
weekend_hours Weekend hours ~69
Saturday and Sunday sales and service hours for every dealer with readable hours, optionally in one county market (e.g. "utah-county") or city, plus the totals. Utah dealers may not sell on both Saturday and Sunday.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| market | string | – | – |
No output schema declared.
No examples provided.
How do I install the Everroad: Utah car dealer facts MCP server?
Everroad: Utah car dealer facts is a hosted endpoint at https://everroad.org/mcp, 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 · everroad.org
claude mcp add --transport http org-everroad-dealers 'https://everroad.org/mcp'
What is the Everroad: Utah car dealer facts MCP server?
Everroad: Utah car dealer facts is an MCP server listed in the public MCP registry as org.everroad/dealers. Utah franchise car dealer facts with sources: hours, weekend service, doc fees, services. This page covers its hosted endpoint (https://everroad.org/mcp).
Is the Everroad: Utah car dealer facts MCP server safe to use?
Everroad: Utah car dealer facts scores 66 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 Everroad: Utah car dealer facts MCP server expose?
Everroad: Utah car dealer facts exposes 7 tools: find_dealers, dealer_facts, dealer_score, compare_dealers, weekend_hours, and 2 more. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.
Does the Everroad: Utah car dealer facts MCP server require authentication?
No. We connected to Everroad: Utah car dealer facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Everroad: Utah car dealer facts MCP server still maintained?
Everroad: Utah car dealer facts is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.