Sigo Seguros car insurance quotes

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "sigo-seguros-car-insurance-quotes": {
      "type": "http",
      "url": "https://mcp.sigoseguros.com/mcp"
    }
  }
}

12 tools

• list_available_states

  Before the flow, optional: where Sigo quotes. The flow itself is next_question, then start_quote once, then get_quote. The US states Sigo Seguros is licensed to sell car insurance in, and what Sigo is. Ask this before collecting details, so a customer elsewhere is not taken…

• next_question

  Step 1 of 3: call it until ready_to_quote is true, sending back the collected it returns each time and each answer under answer_as.key. Then start_quote. Returns the one question to put to the customer now, in their language, with the options to offer when the field has a fixed…

• find_occupation

  Second-round helper, outside the three steps: turns the customer's words into the occupation code start_quote takes. Turns what the customer said they do into the carrier's own occupation codes. Call it before sending `occupation` on a driver: the catalogue is written in trade…

• start_quote

  Step 2 of 3: call it once, with the collected next_question returned when ready_to_quote was true. It returns a quote_id for get_quote. If it answers quote_in_progress, do not call it again: read the quote_id you already have. Retrying the same call, after a timeout say, is…

• get_quote

  Step 3 of 3: read the quote_id start_quote returned, after poll_after_seconds, until more_carriers_pending is false. Never start_quote again to refresh a result. Reads the estimates for a quote_id returned by start_quote. Carriers answer at different speeds: when…

• resolve_application_link

  Outside the three steps: for a customer who arrives with a Sigo link they already have. Says what a Sigo link points at, how far that application has got, and the one thing the customer has to do next. Call it when someone shows up with a link — from an email, a text, or their…

• carrier_questions

  After the three steps, when to_final_quote.next_call names it: the questions of the estimate the customer picked, or of every carrier at once when get_quote carries firm_prices (then no chosen_quote_id). Then answer_carrier_questions. Returns the questions the carrier asks in…

• answer_carrier_questions

  After carrier_questions: file the answers, passing answers_so_far back each time, until the set is complete. Saves what the customer answered against their application, which is what moves it towards a final quote. Send every answer under the code it came back with, and only…

• other_carrier_questions

  Retired. Do not call it: carrier_questions asks every carrier's questions at once, and get_quote carries the firm prices in firm_prices. Kept so an older conversation that reaches it is told where to go, with the link. It asks nothing and reads nothing.

• answer_other_carrier_questions

  Retired. Do not call it: answer_carrier_questions files the one pass for every carrier, and get_quote carries the firm prices in firm_prices. Kept so an older conversation that reaches it is told where to go, with the link. It files nothing.

• commercial_next_question

  Commercial auto, step 1 of 2: call it until ready_to_submit is true, sending back the collected it returns each time and each answer under answer_as.key. Then submit_commercial_application. For a vehicle a business owns or uses for its work: a contractor's pickup, a delivery…

• submit_commercial_application

  Commercial auto, step 2 of 2: call it once, with the collected commercial_next_question returned when ready_to_submit was true. Do not call it again after it answers: a repeat is usually answered with the earlier request and already_received: true, but that is not guaranteed…

Security scan

Recent checks