Quotor — Home & Auto Insurance Quotes MCP server

• check_eligibilityFree

  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.

• check_late_arrivalsFree

  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").

• check_quote_statusFree

  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.

• get_bind_linkFree

  Generate a single-use secure link, valid for 7 days, and EMAIL it to the customer address already collected in the quote. The tool does the email delivery itself and fails if no valid customer email is on file or Gmail cannot send. Libertas customer texting/SMS is not enabled: this tool does not text and you must never promise a text message. 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 receive their final numbers by email. The bind page reveals the real carrier name (the only place it's revealed).

• get_option_detailsFree

  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.

• get_quote_optionsFree

  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).

• request_bind_inlinewrite actionFree

  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.

• resume_quoteFree

  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.

• start_quoteFree

  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.

• submit_leadwrite actionFree

  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]").

• update_quotewrite actionFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1981ms20/20
• Tool poisoning11 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 73 days ago12/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

83/100

higher than 65% of 48,255 servers

Tools

11

the typical server has 7

Tools that change things

27%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

525 ms

faster than 28% of 30,031 servers

GitHub stars

1

more than 65% of 28,688 servers

Quotor — Home & Auto Insurance Quotes: common questions

Is Quotor — Home & Auto Insurance Quotes MCP server safe?

Mostly: it is graded B (83/100). Read the Quotor — Home & Auto Insurance Quotes safety report

How do I install Quotor — Home & Auto Insurance Quotes?

It runs remotely at mcp.quotor.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Quotor — Home & Auto Insurance Quotes need an API key?

Yes. The registry entry asks for Authorization.

Is Quotor — Home & Auto Insurance Quotes maintained?

The last commit was 113 days ago (2026-07-14). The latest release is v0.3.0.

Is Quotor — Home & Auto Insurance Quotes up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Quotor — Home & Auto Insurance Quotes compare with other MCP servers?

safety score 83/100 (higher than 65% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 27% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.