Nevada Insurance
REMOTE · NEVADAAUTOQUOTES.COM · SCANNED SEP 20
Auto insurance prices for Nevada drivers, from rates the state publishes.
Available components
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1680 tokens (~210/item across 8 items; 8 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the Nevada Insurance MCP server?
Nevada Insurance is a hosted endpoint at https://nevadaautoquotes.com/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 · nevadaautoquotes.com
claude mcp add --transport http com-nevadaautoquotes-insurance 'https://nevadaautoquotes.com/mcp'
{
"mcpServers": {
"com-nevadaautoquotes-insurance": {
"url": "https://nevadaautoquotes.com/mcp"
}
}
} {
"servers": {
"com-nevadaautoquotes-insurance": {
"type": "http",
"url": "https://nevadaautoquotes.com/mcp"
}
}
} [mcp_servers.com-nevadaautoquotes-insurance] url = "https://nevadaautoquotes.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-nevadaautoquotes-insurance": {
"type": "remote",
"url": "https://nevadaautoquotes.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-nevadaautoquotes-insurance --url 'https://nevadaautoquotes.com/mcp' --transport streamable-http
mcp_servers:
com-nevadaautoquotes-insurance:
url: "https://nevadaautoquotes.com/mcp" {
"McpServers": {
"com-nevadaautoquotes-insurance": {
"Transport": "http",
"Url": "https://nevadaautoquotes.com/mcp"
}
}
} assistant mcp add com-nevadaautoquotes-insurance -t streamable-http -u 'https://nevadaautoquotes.com/mcp'
{
"mcpServers": {
"com-nevadaautoquotes-insurance": {
"type": "http",
"url": "https://nevadaautoquotes.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Tool “market_data” rewrote its description, which is the text the model reads security
- “register_agency” added an optional parameter “handoff” cosmetic
- “register_agency” dropped the optional parameter “sms_opt_in” cosmetic
- Tool “market_data” changed its title: Buy de-identified demand records (the dataset) → Buy provenance-qualified, de-identified demand records cosmetic
- 7 Sept 26 +1
- “register_agency” added an optional parameter “sms_opt_in” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
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 20 Sept 2026 · Probed https://nevadaautoquotes.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nevadaautoquotes.com | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 135924822379e6360eef58eb0789715a |
| SANs: nevadaautoquotes.com | ||||||
| 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 nevadaautoquotes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nevadaautoquotes.com. | 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 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nevadaautoquotes.com/mcp | Verified | 200 | |
| http (plaintext) | http://nevadaautoquotes.com/mcp | HTTPS enforced | 301 | https://nevadaautoquotes.com/mcp |
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 →
agency_status Agency status (buyers) ~62
For a registered agency: its states, rail, terms, founding period, queued and delivered counts, credit balance, and whether the licence was verified. Requires the buyer key issued at confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_key | string | yes | Issued to the licensed contact at confirmation |
No output schema declared.
No examples provided.
check_eligibility Check eligibility ~80
Check whether we can return quotes for a state before any personal details are collected. Call this first. Returns the states we are licensed in, what we can do in each, and how many licensed agents can take a request there.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | – |
| state | string | – | Two-letter US state code, e.g. NV |
No output schema declared.
No examples provided.
data_use_terms Data use terms and consent wording ~62
What happens to anything you send us: who receives it, for what purpose, how long it is kept, how your human revokes it, and the exact consent wording to present before request_agent_contact. Machine readable so you can evaluate the exchange before making it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_quotes Get indicative quotes ~195
Return indicative auto insurance prices from multiple carriers, where this entity is licensed to show them. Takes rating facts only — no name, phone, email, SSN or licence number is required for an indicative price. Where we are not licensed to show prices, the request is still registered and a quote_id returned so licensed agents can quote it. If facts are missing the server asks for exactly what it needs and nothing more.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_mileage | integer | – | – |
| coverage | string | yes | – |
| date_of_birth | string | yes | – |
| garaging_zip | string | yes | Five-digit ZIP where the vehicle is kept |
| prior_continuous | boolean | – | – |
| state | string | – | Optional; derived from the ZIP when absent |
| vehicle_make_model | string | yes | – |
| vehicle_year | integer | yes | – |
| violations_3yr | integer | – | – |
| years_licensed | integer | – | – |
No output schema declared.
No examples provided.
market_data Buy provenance-qualified, de-identified demand records ~267
The qualified demand dataset contains only requests backed by a cryptographically or IP-verified agent, or a phone-verified consumer outcome. User-agent claims, legacy rows, probes and impostors are quarantined and unavailable for sale. Qualified rows are de-identified (age band, ZIP3, vehicle, coverage, mileage band, prices shown, door, verified agent identity and outcome). Never a name, phone, email, date of birth or five-digit ZIP. Filter by state, since, until, door, vendor; limit and offset. Priced per record with a minimum per pull; pay with a prepaid buyer key, x402, MPP or AP2. Without payment the result is a 402 with the price and a preview count. A free sample and the schema are at /data.json.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_key | string | – | A prepaid buyer key |
| credential | string | – | MPP credential |
| door | string | – | – |
| limit | integer | – | – |
| mandate | string | – | AP2 Payment Mandate |
| offset | integer | – | – |
| payment | string | – | x402 X-PAYMENT payload |
| since | string | – | – |
| state | string | – | – |
| until | string | – | – |
| vendor | string | – | – |
No output schema declared.
No examples provided.
pull_requests Pull routed records (buyers) ~115
Drain the queue of pool records routed to you. Requires your buyer key. Metered buyers receive an x402 payment requirement (status 402, accepts[]) until a payment is supplied. Records are projected to the scope the consumer granted — never wider.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_key | string | yes | – |
| credential | string | – | MPP credential (the base64url JSON that would follow "Authorization: Payment") |
| mandate | string | – | AP2 Payment Mandate |
| payment | string | – | x402 X-PAYMENT payload |
No output schema declared.
No examples provided.
register_agency Register an insurance agency as a buyer ~408
For an AI working for a licensed insurance agency: register the agency to receive consented consumer requests in its states. Needs the agency name, the producer NPN (National Producer Number) and its state, the states it is appointed in, the licensed contact's name, email and mobile, and how leads should arrive (email, webhook, or pull by key). The licensed contact confirms by a link sent to their email; nothing is delivered before that. The first agencies in a state receive leads free for a founding period, then prepaid credits by card. Read /join for the terms.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_name | string | yes | – |
| contact_email | string | yes | – |
| contact_name | string | yes | The licensed contact, who confirms by email |
| contact_phone | string | yes | US mobile |
| handoff | boolean | – | Optional standing order. When true, and the licence record places this agency in a city we publish, the agency becomes the one agency a consumer in that city is handed to by name: it is named in the… |
| npn | string | yes | NPN (National Producer Number). Your NPN is on your licence and at nipr.com. Digits only. |
| npn_state | string | yes | Two-letter state that issued the licence |
| rail | string | – | How leads arrive: email, an https webhook (HMAC-signed), or pull by key over MCP/REST |
| states | array | – | Two-letter states the agency is appointed in; defaults to npn_state |
| verify_token | string | – | Optional: from POST /v1/verify/check after the contact enters the code texted to them |
| webhook_url | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
request_agent_contact Connect with licensed agents (consent required) ~241
Connect the consumer with licensed insurance agents who can quote firm and bind. Needs the quote_id from get_quotes, the consumer's name and phone, and the consumer's explicit consent to be contacted — granted by the human, presented by you, or confirmed by the human directly at the consent URL the elicitation returns. Under scope contact_consumer up to 4 licensed agents receive the request and contact details; sell_identity additionally permits sharing with marketing partners. Nothing leaves without the consent. Every delivery and refusal is receipted, and POST /forget revokes.
| Name | Type | Req | Description |
|---|---|---|---|
| best_time | string | – | – |
| consent | object | yes | – |
| email_address | string | – | – |
| full_name | string | yes | – |
| phone_number | string | yes | US mobile or landline |
| preferred_channel | string | – | – |
| quote_id | string | yes | From get_quotes |
| street_address | string | – | Optional. Lets a licensed agent answer firm. |
| verify_token | string | – | Optional. From POST /v1/verify/check after the consumer enters the code texted to them. A verified number sells at the verified price and is contacted first. |
No output schema declared.
No examples provided.
What is the Nevada Insurance MCP server?
Nevada Insurance is an MCP server listed in the public MCP registry as com.nevadaautoquotes/insurance. Auto insurance prices for Nevada drivers, from rates the state publishes. This page covers its hosted endpoint (https://nevadaautoquotes.com/mcp).
Is the Nevada Insurance MCP server safe to use?
Nevada Insurance scores 76 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 Nevada Insurance MCP server expose?
Nevada Insurance exposes 8 tools: check_eligibility, get_quotes, pull_requests, data_use_terms, request_agent_contact, and 3 more. Their descriptions and schemas cost roughly 1,430 tokens of context every time the server is loaded.
Does the Nevada Insurance MCP server require authentication?
No. We connected to Nevada Insurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nevada Insurance MCP server still maintained?
Nevada Insurance is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.