Skip to content

Coverage Cat

by coveragecat.com · remote · no sign-in to list tools · v1.0.0 · published by com.coveragecat

Get umbrella and homeowners insurance quotes, select a policy, and bind coverage.

Deletes · 9Changes · 8

23 tools: 9 can delete or cancel things, 8 change things and 6 only read.

Scanned Oct 21, 2026

14 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http insurance https://www.coveragecat.com/api/consumer/mcp

Findings

Matches of fixed checks, with the text they matched.

14 info
Show 8 more findings

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

23 tools

Deletes or cancels 9Claude Code: deny
  • consumer_intake_patchPatch or submit a consumer-prefill homeowners or umbrella handoff in chat.1 finding

    Why it is in this group

    • The name "consumer_intake_patch" says "patch": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the default consumer-operated..."

      What this check looks for
    Description, as the server wrote it
    Patch or submit 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. Stay on the default consumer-operated subset. 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, and after submission use `message_reply` plus optional `reply_to_message_id` for insurer or shopper follow-up surfaced under `conversation.messages`. For umbrella, use the staged review turn to send only explicitly missing shopper-owned details plus corrections, set `confirm_submission` only on that final review confirmation, do not send vehicles rows on this pre-submit patch, and do not ask for umbrella credit consent here. Normalize shopper birthdays from MM-DD-YYYY to YYYY-MM-DD, and tell the shopper the application is not submitted yet until you actually submit it. Returns the same follow-up payload as `consumer_intake_issues` for the updated intake.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • homeowners_consumer_bindConfirm the previewed homeowners offer after `homeowners_consumer_select` returns `ready_to_finalize`.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Reuse the returned preview_token, set..."

      What this check looks for
    Description, as the server wrote it
    Confirm the previewed homeowners offer after `homeowners_consumer_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. Reuse the returned preview_token, set bind_confirmed: true, and stay on the same consumer-operated follow-up tool set. Coverage Cat cannot collect homeowners payment in chat; any carrier payment or signing link is emailed to the customer's email on file.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • homeowners_consumer_selectContinue the consumer-prefill homeowners flow after quotes are ready.1 finding

    Why it is in this group

    • The name "homeowners_consumer_select" says "select": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • homeowners_consumer_servicePreview or open a cancellation, refund, or support request for a consumer homeowners policy.1 finding

    Why it is in this group

    • The description's first verb is "preview": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • umbrella_consumer_attachUpload declarations or auto declarations during the consumer-prefill umbrella post-choose flow.1 finding

    Why it is in this group

    • The name "umbrella_consumer_attach" says "attach": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • umbrella_consumer_bindContinue the consumer-prefill umbrella bind follow-up only after select returns needs_more_info_to_bind or ready_to_finalize.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • umbrella_consumer_paymentPrepare secure Stripe payment collection or submit the resulting payment method during the consumer-prefill umbrella post-choose flow.1 finding

    Why it is in this group

    • The name "umbrella_consumer_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • umbrella_consumer_selectContinue the consumer-prefill umbrella flow after quotes are ready.1 finding

    Why it is in this group

    • The name "umbrella_consumer_select" says "select": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • umbrella_consumer_servicePreview or open a cancellation, refund, or support request for a consumer umbrella policy.1 finding

    Why it is in this group

    • The description's first verb is "preview": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the same consumer-operated MCP..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
Changes things 8Claude Code: ask
  • auto_estimatesEstimate monthly auto premiums for one driver and vehicle profile across several carriers.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate monthly auto premiums for one driver and vehicle profile across several carriers. Returns each carrier's id, name, and monthly premium spread (lowest, lower, median, upper, and highest modeled premium) in US dollars, plus the normalized inputs the model used. These are model estimates for research, not bindable quotes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • collision_and_comprehensive_coverageEstimate what collision and comprehensive coverage cost for one driver and vehicle profile, to help decide whether to carry them.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate what collision and comprehensive coverage cost for one driver and vehicle profile, to help decide whether to carry them. Returns monthly premium spreads in US dollars with no physical-damage coverage, collision only, and both, plus collision-only and both after one claim, and cumulative premium projections for each coverage option over projection_years. These are model estimates, not bindable quotes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • consumer_intake_issuesContinue a consumer-prefill homeowners or umbrella handoff in chat.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Stay on the default consumer-operated..."

      What this check looks for
    Description, as the server wrote it
    Continue a consumer-prefill homeowners or umbrella handoff in chat. Returns the intake's status and detail_status, whether the application is submitted, the staged review and next_question, quoted offers with their selection_token, and any post-choose, payment, policy, or conversation state. 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 default consumer-operated subset and, before submission, say explicitly that the application is not submitted yet. For homeowners, treat `missing_fields` as hidden enrichment backlog, keep recovering context-backed facts, reserve one final review turn, and use `consumer_intake_patch` with `message_reply` when `conversation.reply_pending` surfaces insurer or shopper follow-up. 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 instead of re-keying reviewed values. 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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • file_a_claimEstimate whether filing an auto collision claim costs more than paying for the repair yourself.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate whether filing an auto collision claim costs more than paying for the repair yourself. Returns monthly premium spreads with and without one claim, the monthly and multi-year premium increase, the collision deductible, the total cost of filing (deductible plus premium increase), and a file_claim or pay_out_of_pocket recommendation with the estimated savings. These are model estimates, not carrier quotes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • home_calculatorEstimate annual and monthly home insurance ranges for a California property and return the normalized inputs, available risk-factor ids, and ZIP-level context notes that explain th…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate annual and monthly home insurance ranges for a California property and return the normalized inputs, available risk-factor ids, and ZIP-level context notes that explain the estimate.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • homeowners_consumer_prefillPreferred 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.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Homeowners payment or signing links mu..."

      What this check looks for
    Description, as the server wrote it
    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 enrich from user-controlled context and property sources before handing off to Coverage Cat. Recover core shopper and occupancy facts from that context before relying on estimated review data. Stay on the same consumer-operated subset through review, quote polling, `homeowners_consumer_select`, `homeowners_consumer_bind`, `homeowners_consumer_policy`, and `homeowners_consumer_service`. Homeowners quotes or carrier bind follow-up may take up to 48 hours. If `consumer_intake_issues` returns `conversation.reply_pending`, answer 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. Homeowners payment or signing links must be sent to the customer's own email inbox on file. Until submission, tell the shopper the application is not submitted yet.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • umbrella_calculatorResearch-only estimate of annual personal umbrella pricing bands, the inferred risk class, and per-factor impacts for directional pricing.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Research-only estimate of annual personal umbrella pricing bands, the inferred risk class, and per-factor impacts for directional pricing. Use this for price exploration, not when the shopper wants Coverage Cat to shop for or buy umbrella insurance.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • umbrella_consumer_prefillPreferred 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.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Until later follow-up shows progress,..."

      What this check looks for
    Description, as the server wrote it
    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 and assemble the fullest justified estimate from user-controlled context. Use canonical umbrella keys such as address.street/city/state/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. Do not send vehicles rows before submission. Stay on the same consumer-operated subset through `consumer_intake_issues`, `consumer_intake_patch`, `umbrella_consumer_select`, `umbrella_consumer_bind`, `umbrella_consumer_attach`, `umbrella_consumer_payment`, `umbrella_consumer_policy`, and `umbrella_consumer_service`. 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 the same shopper-safe 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. Until later follow-up shows progress, tell the shopper the application is not submitted yet. 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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
Only reads 6Claude Code: allow
  • docs_get_resourceRead one Coverage Cat docs resource by URI from the default consumer MCP and return its URI, public href (null when it has no public page), MIME type, and full markdown, JSON, or Y…No findings

    Why it is in this group

    • The name "docs_get_resource" says "get": a word for reading.
    Description, as the server wrote it
    Read one Coverage Cat docs resource by URI from the default consumer MCP and return its URI, public href (null when it has no public page), MIME type, and full markdown, JSON, or YAML text.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • docs_list_topicsList Coverage Cat documentation topics from the same consumer MCP connection and return each topic's title, category, URI, MIME type, summary, and public href.No findings

    Why it is in this group

    • The name "docs_list_topics" says "list": a word for reading.
    Description, as the server wrote it
    List Coverage Cat documentation topics from the same consumer MCP connection and return each topic's title, category, URI, MIME type, summary, and public href.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • homeowners_agent_finderFind licensed homeowners insurance agents near a ZIP code using state department of insurance licensing data.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find licensed homeowners insurance agents near a ZIP code using state department of insurance licensing data. California searches return agents within 75 miles, nearest first; Texas searches return agents in the same ZIP. ZIP codes in other states return an empty agents list alongside supported_states. Each agent record includes name, agency, license, lines, location, contact details, and source links.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • homeowners_consumer_policyRead the current bound or cancelled homeowners policy record, policy documents, and any existing cancellation, refund, or support request history.1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Use this read-only tool after Coverage..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • umbrella_consumer_policyRead the current bound or cancelled umbrella policy record, policy documents, and any existing cancellation, refund, or support request history.1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...g to raw HTTP or asking the shopper for credentials. Use this read-only tool after Coverage..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http insurance https://www.coveragecat.com/api/consumer/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__insurance__umbrella_consumer_policy",
      "mcp__insurance__homeowners_consumer_policy",
      "mcp__insurance__homeowners_agent_finder",
      "mcp__insurance__docs_list_topics",
      "mcp__insurance__docs_search",
      "mcp__insurance__docs_get_resource"
    ],
    "ask": [
      "mcp__insurance__umbrella_consumer_prefill",
      "mcp__insurance__homeowners_consumer_prefill",
      "mcp__insurance__consumer_intake_issues",
      "mcp__insurance__home_calculator",
      "mcp__insurance__umbrella_calculator",
      "mcp__insurance__auto_estimates",
      "mcp__insurance__collision_and_comprehensive_coverage",
      "mcp__insurance__file_a_claim"
    ],
    "deny": [
      "mcp__insurance__consumer_intake_patch",
      "mcp__insurance__umbrella_consumer_select",
      "mcp__insurance__umbrella_consumer_bind",
      "mcp__insurance__umbrella_consumer_attach",
      "mcp__insurance__umbrella_consumer_payment",
      "mcp__insurance__umbrella_consumer_service",
      "mcp__insurance__homeowners_consumer_select",
      "mcp__insurance__homeowners_consumer_bind",
      "mcp__insurance__homeowners_consumer_service"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as insurance. Review it before you use it.