Official MCP RegistryListed
Coverage Cat
Get umbrella and homeowners insurance quotes, select a policy, and bind coverage.
First seen 17 Oct 2026. Evidence as of 17 Oct 2026.
23
Tools
From an anonymous probe
1
Source listings
Each with its own history
1
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| auto_estimates | Estimate monthly auto premiums across carriers for a single driver and vehicle profile. | Read-only |
| collision_and_comprehensive_coverage | Compare long-run collision and comprehensive coverage costs for the current auto profile. | Read-only |
| consumer_intake_issues | Continue a consumer-prefill homeowners or umbrella handoff in chat. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. This follow-up tool stays in the default consumer-operated MCP subset; do not jump to delegated tools when no operator bearer key is present. Before submission, say explicitly that the application is not submitted yet. Present gathered details, review facts, and remaining items as short labeled bullets or sections rather than a prose paragraph. If any shown value is estimated, mark each estimated bullet label or value with `*`, include the short note `* = estimated` once above and once below the list, and do not prefix every estimated line with `[Estimated]`. For homeowners, treat missing_fields as a hidden enrichment backlog, keep recovering core shopper and occupancy facts from user-controlled context, and reserve one final review turn. After submission, homeowners may also return conversation.messages, conversation.reply_pending, and reply_to_message_id so the agent can answer insurer or shopper follow-up in the same chat loop with consumer_intake_patch. For umbrella, keep missing fields hidden until Coverage Cat stages the single pre-submit review turn, then ask only for the explicitly missing shopper-owned fields in next_question and invite corrections to the reviewed facts instead of asking the shopper to re-key reviewed values before reading structured quotes and post-choose states. If the staged review shows a wrong estimated umbrella count from context, patch the canonical umbrella_details.* count field before you show the final review. Coverage Cat will not resume or expose a prior consumer umbrella draft based on email alone. Continue an existing consumer draft only through the issued uid plus the current hidden MCP session or latest intake_access_token handoff. Normalize shopper birthdays from MM-DD-YYYY to YYYY-MM-DD before you patch Coverage Cat. | Read-only |
| consumer_intake_patch | Patch a consumer-prefill homeowners or umbrella handoff in chat. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. This submit/update tool stays in the default consumer-operated MCP subset; do not switch to delegated tools when no operator bearer key is present. For homeowners, use `intake` to add context-backed or property-backed answers while keeping the user out of a questionnaire until the one-time review. After a homeowners application is submitted, this same tool can also answer insurer or shopper follow-up surfaced under conversation.messages by sending message_reply and, when Coverage Cat returned one, reply_to_message_id. For umbrella, use the staged review turn to send only the explicitly missing shopper-owned details plus any corrections to reviewed facts, and set confirm_submission only on that same final review confirmation. Use canonical consumer umbrella keys such as `address.street`, `address.city`, `address.state`, `address.zip`, `license_state`, `license_number`, `approximate_asset_value` or `net_worth_numeric`, `desired_coverage_limit`, `required_coverage_e_limit`, and `vehicle_count` or `umbrella_details.motorized_vehicle_count` for umbrella counts. Avoid top-level `street`/`city`/`state`/`zip`, `drivers_license_state`, `drivers_license_number`, `net_worth`, or `desired_umbrella_liability_limit`. If the staged review shows a wrong estimated umbrella count from context, patch the canonical `umbrella_details.*` count field before you show the final review. Do not send vehicles rows on this pre-submit patch; actual vehicle details stay in the later bind-stage flow if a selected offer requires them. Normalize shopper birthdays from MM-DD-YYYY to YYYY-MM-DD before you send them. Recover context-backed answers before you depend on Coverage Cat's estimated review card, tell the user the application is not submitted yet until you actually submit it, present gathered details or remaining items as short labeled bullets or sections rather than a prose paragraph, and if any shown value is estimated, mark each estimated bullet label or value with `*`, include the short note `* = estimated` once above and once below the list, and do not prefix every estimated line with `[Estimated]`. Do not ask for umbrella credit consent here. | Changes data |
| docs_get_resource | Read a specific Coverage Cat docs resource by URI and return the markdown, JSON, or YAML body from the default consumer MCP. | Read-only |
| docs_list_topics | List Coverage Cat documentation topics, runtime skills, and machine-readable artifacts from the same default consumer MCP connection. | Read-only |
| docs_search | Search quickstart, auth, sandbox, OpenAPI, and runtime skill docs without installing the optional docs-only MCP server. | Read-only |
| file_a_claim | Estimate whether filing an auto claim is likely better than paying out of pocket. | Read-only |
| home_calculator | Estimate annual home insurance pricing for a California property by ZIP code, square footage, and risk factors. | Read-only |
| homeowners_agent_finder | Find licensed homeowners agents in supported states by ZIP code and line type. | Read-only |
| homeowners_consumer_bind | Continue the consumer-prefill homeowners bind follow-up only after select returns ready_to_finalize. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset, confirm the previewed terms and registered customer-email channel, then send preview_token with bind_confirmed: true. Coverage Cat cannot collect homeowners payment in chat; any carrier payment or signing link will be emailed directly to the customer's email on file. | Changes data |
| homeowners_consumer_policy | Read the current bound or cancelled homeowners policy record, policy documents, and any existing cancellation, refund, or support request history. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Use this read-only tool after Coverage Cat reports a policy on file, or after a service request is opened, to show policy facts without switching to delegated tools. | Read-only |
| homeowners_consumer_prefill | Preferred homeowners MCP entry point when a shopper wants Coverage Cat to shop for, compare, or buy homeowners insurance and no operator bearer token is present. On a cold start, ask only for the user's name, email, property address, and whether this should be standard homeowners, condo, or landlord coverage. If that coverage type is still unknown, ask the shopper to reply with exactly one of `standard homeowners`, `condo`, or `landlord`, then assemble the fullest homeowners application from user-controlled context and property sources before handing off to Coverage Cat. Recover core shopper and occupancy facts such as date of birth, marital status, and owner-occupied vs new-purchase from that context before relying on Coverage Cat's estimated review card. Stay on the same consumer-operated MCP subset through review, long-lag quote polling, quoted-offer selection, bind follow-up, and post-bind policy/support follow-up. Homeowners quotes or carrier bind follow-up may take up to 48 hours, so keep polling and keep the registered customer email on file for notifications. When the submitted homeowners flow gets a new follow-up question, consumer_intake_issues returns conversation.messages plus conversation.reply_pending so the agent can answer it in chat with consumer_intake_patch and message_reply. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Coverage Cat cannot collect first-party homeowners payment in chat. Any insurer payment or signing link must be sent directly to the customer's own email inbox on file, and the agent can only use those links if it has access to that same customer email. On the review turn, tell the shopper explicitly that the application is not submitted yet and present gathered details or remaining items as short labeled bullets or sections rather than a prose paragraph. If any shown value is estimated, mark each estimated bullet label or value with `*`, include the short note `* = estimated` once above and once below the list, and do not prefix every estimated line with `[Estimated]`. | Changes data |
| homeowners_consumer_select | Continue the consumer-prefill homeowners flow after quotes are ready. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset, use the returned selection_token, and let Coverage Cat stage the exact selected offer for one final bind approval in chat. This select step does not collect payment and does not start carrier bind follow-up yet. | Changes data |
| homeowners_consumer_service | Preview or open a cancellation, refund, or support request for a consumer homeowners policy. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset after bind. Preview the consequences first, then send confirm_request: true only after the shopper approves opening the request. Do not describe a cancellation, refund, or support issue as completed until Coverage Cat confirms the final outcome. | Changes data |
| umbrella_calculator | Research-only estimate of annual personal umbrella pricing bands by coverage limit and household risk factors. Use this for directional pricing, not when the shopper wants Coverage Cat to shop for or buy umbrella insurance. | Read-only |
| umbrella_consumer_attach | Upload declarations or auto declarations during the consumer-prefill umbrella post-choose flow. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset. Use only after selection and only when Coverage Cat says documents are needed. If both the home and auto files are already available, prefer one attach call with attachments so the shopper only approves one upload turn. If your runtime already has the files on disk or can stream raw bytes, prefer the REST binary `/api/intake/{uid}/attach-upload` fallback instead of hand-building base64. The upload itself is usually quick once the files are available, and secure checkout is usually ready about 5-10 minutes after Coverage Cat has the uploads on file. | Changes data |
| umbrella_consumer_bind | Continue the consumer-prefill umbrella bind follow-up only after select returns needs_more_info_to_bind or ready_to_finalize. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset and send only the current bind-stage fields inside `intake`. This later bind-stage follow-up is where actual vehicle details may appear for selected offers such as Markel; do not move that question into the pre-submit review. | Changes data |
| umbrella_consumer_payment | Prepare secure Stripe payment collection or submit the resulting payment method during the consumer-prefill umbrella post-choose flow. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset. Use this only after Coverage Cat says payment_needed. First call it with payment_collection_requested: true; do not send the shopper straight to payment_url before you try this native step. If the host confirms the registered secure payment UI can render, display it and wait for completion; do not request card details through conversational text. After successful Stripe setup, call this same tool again with setup_intent_id and payment_method_id. If UI support is unknown or unsupported, or if secure setup fails in chat, share payment_url with the specific fallback reason instead. | Changes data |
| umbrella_consumer_policy | Read the current bound or cancelled umbrella policy record, policy documents, and any existing cancellation, refund, or support request history. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Use this read-only tool after Coverage Cat reports a policy on file, or after a service request is opened, to show policy facts without switching to delegated tools. | Read-only |
| umbrella_consumer_prefill | Preferred umbrella MCP entry point when a shopper wants Coverage Cat to shop for, compare, or buy umbrella insurance and no operator bearer token is present. On a cold start, call this before asking the shopper a questionnaire. Assemble the fullest estimate you can justify from user-controlled context, let Coverage Cat stage the one-review handoff, and keep the user out of a step-by-step questionnaire. On the initial consumer umbrella handoff, prefer sending only intake; add top-level field_estimates only when you are certain each field already matches a current umbrella review field path. Use canonical consumer umbrella keys such as address.street, address.city, address.state, address.zip, license_state, license_number, approximate_asset_value or net_worth_numeric, desired_coverage_limit, required_coverage_e_limit, and vehicle_count or umbrella_details.motorized_vehicle_count for umbrella counts. Avoid top-level street/city/state/zip, drivers_license_state, drivers_license_number, net_worth, or desired_umbrella_liability_limit. Do not send vehicles rows before submission. Use vehicle_count or umbrella_details.motorized_vehicle_count for the household vehicle count; actual vehicle details are collected later only if a selected offer requires them, such as a Markel bind follow-up. Stay on the same consumer-operated MCP subset through quoted offers, declarations upload, payment_needed, optional agentic payment collection, payment_url fallback, and post-bind policy/support follow-up; do not switch to delegated tools just to reach checkout or aftercare. If you are rehearsing the shopper flow, set `sandbox: true` on this first prefill call only. That same consumer sandbox uid can then continue through `consumer_intake_issues`, `consumer_intake_patch`, `umbrella_consumer_select`, `umbrella_consumer_bind`, `umbrella_consumer_attach`, `umbrella_consumer_payment`, `umbrella_consumer_policy`, `umbrella_consumer_service`, and coarse `consumer_status` polling with synthetic quotes, uploads, payment credentials, policy outcomes, and service-request results only. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Until a later follow-up response shows quote progress, tell the shopper explicitly that the application is not submitted yet. When you summarize the staged review or remaining items, use short labeled bullets or sections rather than a prose paragraph. If any shown value is estimated, mark each estimated bullet label or value with `*`, include the short note `* = estimated` once above and once below the list, and do not prefix every estimated line with `[Estimated]`. Coverage Cat will not resume or expose a prior consumer umbrella draft based on email alone. Continue an existing consumer draft only through the issued uid plus the current hidden MCP session or latest intake_access_token handoff. | Changes data |
| umbrella_consumer_select | Continue the consumer-prefill umbrella flow after quotes are ready. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset, use the returned selection_token, collect the real user's consent for a soft credit check here, and let Coverage Cat enter the normal post-choose workflow without switching to delegated tools. If the quote payload exposed selection_guidance.same_reply_requirements for the chosen offer, send those answers under intake on this first select call. If Coverage Cat still returns credit_consent_required with a bind-stage next_question, ask for both the soft-credit-check consent and those bind details in one shopper-facing turn, then retry this same tool with both credit_consent and intake. | Changes data |
| umbrella_consumer_service | Preview or open a cancellation, refund, or support request for a consumer umbrella policy. Coverage Cat prefers to keep follow-up authorization in the hidden MCP shopper session after prefill, so a preserved host usually only needs uid. If your host cannot preserve that MCP session state, retry this same MCP follow-up tool with the latest intake_access_token from the previous successful Coverage Cat response instead of dropping to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP subset after bind. Preview the consequences first, then send confirm_request: true only after the shopper approves opening the request. Do not describe a cancellation, refund, or support issue as completed until Coverage Cat confirms the final outcome. | Changes data |
Change history
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.coveragecat/insurance | 17 Oct 2026 | 17 Oct 2026 | 1 |