# Quotor — Home & Auto Insurance Quotes (remote · mcp.quotor.ai)

Real, bindable home & auto insurance quotes via MCP (Texas, expanding); human-completed bind.

- Trust score: 57/100 (low)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.quotor.ai`: 57/100 (this document), [markdown](https://verifymcp.io/servers/quotor-home-auto-insurance-quotes/mcp.md), [page](https://verifymcp.io/servers/quotor-home-auto-insurance-quotes/mcp)

## Channel facts

- Endpoint: `https://mcp.quotor.ai`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 24/100
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 3417 tokens (~310/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http quotor-home-auto-insurance-quotes https://mcp.quotor.ai/
```

### Codex

```toml
[mcp_servers.quotor-home-auto-insurance-quotes]
url = "https://mcp.quotor.ai/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quotor-home-auto-insurance-quotes": {
      "type": "remote",
      "url": "https://mcp.quotor.ai/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add quotor-home-auto-insurance-quotes --url https://mcp.quotor.ai/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  quotor-home-auto-insurance-quotes:
    url: "https://mcp.quotor.ai/"
```

### Other

```json
{
  "mcpServers": {
    "quotor-home-auto-insurance-quotes": {
      "type": "http",
      "url": "https://mcp.quotor.ai/"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 57, +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.

### 2026-07-31 (score 56, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 54, +1)

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

### 2026-07-28 (score 53, +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.

### 2026-07-27 (score 52, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 52)

First indexed and scored.

## MCP tools (11)

### `check_eligibility` (~151 tokens)

Confirm whether Libertas can quote and bind insurance for the customer in their state. Call this first — before collecting any personal details — when the customer asks about insurance prices, switching carriers, or shopping for coverage. State is supplied automatically from the request context (the platform's location consent flow); you don't need to ask the customer for state to call this. Returns whether quoting is available, whether binding is available, and a plain-language explanation the customer can read.

Input parameters:

- `intent` (string): Whether you're checking ability to 'quote' or to 'bind' (default 'quote').
- `product` (string, required): Line of business: 'auto', 'home', or 'bundle' (home + auto).

Output parameters:

- `can_bind` (boolean)
- `can_quote` (boolean)
- `explanation` (string)
- `next_step` (string)
- `state` (string|null)

### `start_quote` (~465 tokens)

Begin a new home, auto, or bundled insurance quote. Returns a quote ID to use on every following call. Call this when the customer wants to get an insurance price.

INTAKE ORDER (Kyle 2026-06-11 — collect in this order, ONE coherent chunk per turn):
  1\. HOME/BUNDLE: full name + date of birth for EVERYONE on the policy (relationship for non-PNI).
  2\. Address of the home + "is this a new purchase, or one you've owned a while?" (new purchase → ALSO capture current_address — where they live today; property.address stays the home being bought). Then mortgage + escrow + "roughly how old is the roof? — 'I don't know' is a fine answer" ride along (roof unknown → move on, never probe; roof REPLACED → one follow-up: hail-resistant / Class 1–4? → property.hail_resistant_roof + property.ul_impact_type). The home address doubles as auto garaging unless the cars live elsewhere.
  3\. AUTO/BUNDLE: year/make/model of every vehicle.
  4\. Any drivers NOT already named in step 1 — names + DOBs + relationship.
  5\. Email + phone, framed as "where should I send your final numbers?" — the consent line is REQUIRED on this turn.
  6\. ONE open question before firing: "Any coverages you want to tell me about before I run it?" Capture whatever they volunteer via update_quote and move on — do NOT turn this into a coverage consultation. Scheduled valuables (jewelry, art, guns, collections) are a POST-BIND follow-up: record them under the follow_ups patch branch and tell the customer "our team will add that right after we get this policy locked" — never try to add them mid-quote.

Then call get_quote_options immediately. Don't over-collect — the customer should reach prices fast.

Input parameters:

- `meta_codes` (array): Optional internal meta codes; ignored unless recognized.
- `product` (string, required): Line of business to quote: 'auto', 'home', or 'bundle'.
- `referral_source` (string): Optional referral/partner source tag for attribution.

Output parameters:

- `next_required_inputs` (array)
- `quote_id` (string)
- `session_expires_at` (string)

### `update_quote` (~489 tokens)

Set or refine any quote parameter except regulated enrichment fields (credit score, MVR, CLUE, VIN-decoded vehicle attributes, public-record property attributes). Idempotent — call as many times as needed; the most recent value wins. Returns which fields were applied, which were rejected (with reasons), and whether the quote has enough info to run.

WHEN TO CALL:
  \- After collecting the required-minimum from the customer in start_quote
  \- Whenever the customer changes their mind about any coverage, deductible, discount, payment plan, or term length
  \- When the customer shares a declarations page and you have new values to sync

CONVERSATION STYLE for coverages (per Kyle, the agency principal):
  After the first rates land, walk through major coverages one-or-two-at-a-time with a soft-sell framing.
  Example: "You have $200,000 of personal property coverage on this quote — that's the carrier's minimum and you can only go up. Does that sound like enough for your stuff?" Let the customer pick. Then call update_quote with the new value and get_quote_options again — re-quoting is free and fast (10–60 seconds).

REGULATED FIELDS (will be rejected with structured reason):
  drivers[*].license_number, .ssn, .mvr_*, .credit_score; payment fields; carrier name; vin_decoded_attributes. The system pulls these directly from the bureaus at quote time or collects them at bind on libertasinsurance.com.

Input parameters:

- `meta_codes` (array): Optional internal meta codes; ignored unless recognized.
- `patch` (object, required): Free-form patch onto the quote. Top-level branches: pni, drivers[], vehicles[], property, coverages, discounts, policy_terms, prior_insurance, has_mortgagee, mortgage_billed_by_lender, mortgagee, is_…
- `quote_id` (string, required): The quote session id returned by start_quote.

Output parameters:

- `applied` (array)
- `completeness` (number)
- `quote_id` (string)
- `ready_to_quote` (boolean)
- `rejected` (array)

### `get_quote_options` (~282 tokens)

Fire all eligible A-rated carriers in parallel AND kick off live rate-finishing. RETURNS IMMEDIATELY — does NOT wait.

TWO STAGES follow:
  1\. First numbers land in 30–90 seconds. Options surface as honest price RANGES — the low end is the carrier's indicative, so the final verified rate usually lands AT OR BELOW the low end.
  2\. The system keeps working for 2–10 minutes after that, logging into carrier portals and walking each competitive quote to its exact bindable rate. Option cards harden from "estimated range" to "verified" as each carrier completes. check_quote_status reports this via its 'finishing' block.

What you do during the wait: KEEP THE CONVERSATION GOING with the wait-phase playbook in the system prompt (waters first, then current premium — top priority — then claims color, pets, pool, start date, payment preference). Narrate the real finishing work honestly in ONE short line when relevant; never quantify carriers or name them.

Call get_quote_options again ONLY if a rating-changing input changes (waters toggle locally — never re-fire for those).

Input parameters:

- `max_options` (integer): Maximum options to return per line (1-5, default 3).
- `quote_id` (string, required): The quote session id returned by start_quote.

Output parameters:

- `expected_seconds` (integer)
- `message` (string)
- `quote_id` (string)
- `status` (string)

### `check_quote_status` (~437 tokens)

Check rating + live-finishing progress. Call between wait-phase questions (every customer turn or two after get_quote_options). Returns one of:
  \- 'running' — indicatives still landing; continue the wait-phase conversation, call again next turn.
  \- 'quoted' — options[] is populated. CHECK THE 'finishing' BLOCK: when finishing.active=true, the exact bindable rates are STILL being captured live at the carrier portals — present the price ranges confidently as honest estimates (the low end is the carrier's own starting figure; NEVER promise the final number can't exceed the range), keep the conversation going, and keep checking on later turns; cards harden to 'verified' automatically as walks complete. When finishing.active=false, the run is over: cards marked 'verified' are exact bindable numbers; anything still 'estimate' stays a range that a licensed agent confirms at bind.
  \- 'timeout' — carriers took too long; offer to retry with get_quote_options.
  \- 'needs_data' — carriers can't rate until the customer supplies the fields in needs.prompts (e.g. a driver's license number, a VIN, or an additional driver's name/date of birth — each prompt says who/what it's for). Ask the customer conversationally, apply the answers with update_quote (the prompt 'field' values are the exact patch paths, e.g. drivers[1].date_of_birth), then call get_quote_options to re-run. Repeat as many times as it takes — this is an ask, NOT a failure. needs may also ride along with 'quoted' when one line rated and the other still needs info.
  \- 'error' — all carriers errored; flag it honestly and offer to retry.
Each option carries rate_state ('verified' | 'verifying' | 'estimate') and, for unverified options, price_range {low, high}. NEVER mention carrier counts or real carrier names in chat.

Input parameters:

- `max_options` (integer): Maximum options to return per line (1-5, default 3).
- `quote_id` (string, required): The quote session id to poll.

Output parameters:

- `carrier_names_revealed` (boolean)
- `needs` (object|null)
- `options` (array)
- `progress_pct` (integer)
- `quote_id` (string)
- `status` (string)

### `get_option_details` (~97 tokens)

Pull the full coverage breakdown, deductibles, applied discounts, and payment plan options for a single masked option (Home Carrier A, Auto Carrier B, etc.). Use when the customer wants to dig into a specific quote before deciding. Carrier name remains masked.

Input parameters:

- `option_id` (string, required): The option to detail, e.g. 'opt_home_a' from get_quote_options.
- `quote_id` (string, required): The quote session id.

Output parameters:

- `coverages` (object)
- `premium_annual` (number|null)
- `premium_monthly` (number|null)

### `get_bind_link` (~150 tokens)

Generate a single-use secure link, valid for 7 days, that the customer can follow to a Libertas bind-request page. The chat widget will usually render an inline 'Request Bind' card directly — prefer request_bind_inline for the in-chat flow. Use get_bind_link when the customer wants to leave the chat, finish on a different device, or have their final numbers emailed to them (pair it with the email offer during a long finishing wait). The bind link reveals the real carrier name (the only place it's revealed).

Input parameters:

- `option_id` (string, required): The option the customer chose to bind, e.g. 'opt_home_a'.
- `quote_id` (string, required): The quote session id.

Output parameters:

- `bind_url` (string)
- `carrier_name` (string)
- `expires_at` (string)
- `option_id` (string)
- `quote_id` (string)

### `request_bind_inline` (~356 tokens)

Submit the customer's bind request from the chat. Triggers an internal task for our licensed team to follow up. THIS IS NOT INSTANT BIND — no payment is collected and no coverage starts from this call; a licensed agent completes underwriting verification, payment, and carrier confirmation afterward, and the customer can still change or cancel the request. Because this step is non-binding and reversible, the customer's own clear choice ("I'd like to go with Carrier A", "let's do A and A", "I'll take Carrier B") is sufficient confirmation to submit — an additional "are you sure?" prompt is not required, though you should always honor your own platform's confirmation practices. NEVER name a real carrier in chat output — stay in "Carrier A/B/C" labels.

Input parameters:

- `best_time` (string): Best time to reach the customer, e.g. 'weekday afternoons'.
- `contact_pref` (string): How the customer prefers to be reached: 'call', 'text', or 'email'.
- `customer_notes` (string): Optional free-text notes from the customer for the agent.
- `option_id` (string): The single option to bind (or use option_ids for a bundle/split).
- `option_ids` (array): Multi-option bind. Either option_id or option_ids must be provided.
- `pay_plan` (string): Pay plan: 'monthly_eft' or 'pay_in_full' (required when an auto line is included).
- `quote_id` (string, required): The quote session id.
- `water_selections` (object): Customer-selected water-coverage add-ons for home options (service line, water seepage, foundation water, sewer backup); the agent configures these at the carrier portal at bind.

Output parameters:

- `bind_url` (string)
- `quote_id` (string)

### `check_late_arrivals` (~416 tokens)

Save-the-sale tool — call when the customer signals dissatisfaction with the current options ("too expensive", "let me think", "what else do you have", "is this the best you can do", "I'll check elsewhere", "can you do better"). Some carriers (Foremost STAR, etc.) run slower than the initial set and may have come back with a better rate while the customer was deliberating. This tool:

  1\. Pulls a fresh read of all rated carriers.
  2\. Compares the current cheapest bundle/LOB price to the original first-quoted best.
  3\. Returns has_improvement=true ONLY if a late carrier beats the original by >= $100/yr OR >= 5% — a threshold meaningful enough to justify interrupting the customer.

CALL THIS ONLY WHEN:
  \- check_quote_status has returned 'quoted' at least once (there's a baseline to compare).
  \- The customer just expressed price resistance or hesitation (not a closed positive).
  \- You have NOT called check_late_arrivals in the last 2 turns (don't spam).

DO NOT CALL WHEN:
  \- The customer is actively committing ("yeah let's go with A") — that's a close moment, not a wavering moment.
  \- The customer hasn't seen the initial options yet.

WHAT TO DO WITH THE RESULT:
  \- has_improvement=true → narrate the improvement naturally ("Quick update — one more carrier just came in $X/yr cheaper. Want me to refresh your options?") and the iframe auto-updates with the new state.
  \- has_improvement=false → acknowledge the customer's concern, pivot to value positioning against the options on the table. Don't bluff a "better one is coming" if it isn't. Use the carriers_still_pending count if relevant ("a couple more carriers are still finalizing in the background — I'll flag if anything comes in lower").

Input parameters:

- `quote_id` (string, required): The quote session id to check for late-arriving carrier rates.

Output parameters:

- `new_options` (array)

### `submit_lead` (~442 tokens)

Capture a lead for an insurance product Libertas doesn't quote inline (renters, life, commercial, motorcycle, boat, RV, umbrella, condo, landlord, etc.) — OR any home/auto customer who asks to be contacted later instead of finishing the quote in chat. Creates a row in the CRM Leads bucket so a licensed agent can follow up.

CALL THIS WHEN:
  \- The customer asks about an insurance type other than home/auto/bundle, AND has shared a name + email or phone. Confirm with the customer that you're going to have someone reach out, then call this tool.
  \- The customer says "have someone call me later" or similar even on a home/auto inquiry.
  \- The customer mentions an unusual circumstance and wants a human follow-up.

DO NOT CALL WHEN:
  \- The customer is still actively answering questions in the home/auto intake flow — keep going through the regular intake.
  \- You don't have any contact info yet — ask for name + email/phone first.

What it does: writes a Leads row tagged with the line of interest, contact info, preferred follow-up time, and any notes you supply. A licensed Libertas agent will reach out within one business day. Returns a confirmation message you can paraphrase to the customer ("you're on our list — someone from the team will reach out about [interest]").

Input parameters:

- `email` (string): Customer email.
- `first_name` (string): Customer first name.
- `interest` (string, required): What the customer wants us to follow up about (e.g. 'renters insurance', 'life insurance', 'commercial auto')
- `last_name` (string): Customer last name.
- `notes` (string): Optional notes for the follow-up.
- `phone` (string): Customer phone number.
- `preferred_contact_method` (string): How the customer prefers to be reached: 'phone', 'email', 'text', or 'any'.
- `preferred_contact_time` (string): e.g. 'weekday afternoons', 'after 5pm', 'tomorrow morning'
- `quote_id` (string): Optional quote id to associate the lead with.

Output parameters:

- `ok` (boolean)

### `resume_quote` (~132 tokens)

Pick up an existing quote that was started in a previous session or on a different platform. The customer supplies a quote ID. Verification: if the same authenticated user (OAuth user_id matches across sessions), no extra verification is needed; otherwise the customer needs to provide an email code that was sent at quote start. Returns the current status, a summary of what's collected so far, and whether rate options are already available to review.

Input parameters:

- `quote_id` (string, required): The quote session id to resume.
- `verification` (object): Ownership verification (email code, platform identity, or magic link); required to return PII.

Output parameters:

- `quote_id` (string)
- `status` (string)
- `verification_required` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/quotor-home-auto-insurance-quotes/mcp#diagnostics

## Score history

- 2026-08-03: 57
- 2026-08-02: 56
- 2026-08-01: 56
- 2026-07-31: 56
- 2026-07-30: 54
- 2026-07-29: 54
- 2026-07-28: 53
- 2026-07-27: 52
- 2026-07-26: 52

## Links

- Remote endpoint: https://mcp.quotor.ai/
- Repository: https://github.com/quotor/home-auto-insurance-quotes
- Website: https://quotor.ai/
- Changelog RSS feed: https://verifymcp.io/servers/quotor-home-auto-insurance-quotes/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/quotor-home-auto-insurance-quotes/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/quotor-home-auto-insurance-quotes/mcp