wealthmcp.ai
← Back to directory

Alishahi Insurance — Insurance Quote Requests

Alishahi Insurance · Insurance & Annuities

MCP ServerCommunity

Alishahi Insurance’s remote MCP server lists available coverages, retrieves coverage-specific questions and submits quote requests to an independent broker after contact consent. It also lets assistants read and complete applications the broker started from emailed requests. Advisors and client-service staff could use it to coordinate insurance inquiries, with pricing and coverage decisions handled by the broker outside the assistant.

insurancequote requestscoverage discoveryapplication intakeindependent brokerstreamable http
Status
Community
Auth
None
Hosting
Remote
Community rating
Not rated yet
Role
System

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

  • Vendor-reported capabilities and licensing claims have not been independently verified. The vendor welcomes requests from any U.S. state but reports licensing in 48 states and Washington, DC without identifying the two excluded states here.
  • Vendor-reported write actions submit quote requests and complete applications. They do not price insurance, compare premiums, confirm coverage or bind policies; broker review and underwriting remain necessary.
  • The vendor says it receives confirmed contact details and insurance answers, not the rest of the conversation. It advises against sharing identity-document numbers, financial account details or health information in chat and reports screening requests to remove them.
  • The public server requires no authentication, according to the vendor, but reading and completing an existing application requires the application ID and token supplied in the broker’s email.
  • Vendor-reported submission requirements include name, phone, email, coverage and explicit contact consent. Requests are limited to one per email and coverage per day.
  • The vendor documents Claude connector setup but says the ChatGPT app is still being submitted. The page does not establish that direct request submission through a listed ChatGPT app is available.
  • Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server

How to connect Alishahi Insurance — Insurance Quote Requests

Step 1

Remote server: paste a URL

Alishahi Insurance — Insurance Quote Requests publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://alishahiinsurance.com/mcp

Client config snippet

{
  "mcpServers": {
    "c3f24944-b893-493d-89c3-ae2b3b4404ae": {
      "url": "https://alishahiinsurance.com/mcp"
    }
  }
}

Step 2

Authenticate with no credentials

No credentials are required for public data. Rate limits still apply, so avoid bulk pulls from a chat client.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Insurance & Annuities.

Planning data-gathering gap check

What's still missing before a plan can be built.

Financial PlanningFinancial PlanningInsurance & Annuities

Read-only: compare the planning inputs on file for <client name> in the planning tool against what the insurance and annuity records actually show, and list what is missing, stale or inconsistent before I build or update a plan: income, expenses, balances, coverage amounts, riders, premiums, beneficiaries, goals and assumptions. Output Item / Value in plan / Value at source / Status / Last updated. Do not edit the plan or write any assumption, flag gaps and mismatches rather than filling them in.

Guardrail · Read-only. Never let a tool invent a planning assumption.

Insurance and protection gap review

Coverage on file versus what the plan implies.

Financial PlanningInsurance & AnnuitiesFinancial Planning

Read-only: list <client name>'s in-force coverage, life, disability, LTC, annuity riders, with carrier, benefit, term and cost, then compare against the protection need implied by the plan. Flag gaps and expiring coverage. No product recommendations and no applications. Note where policy data could not be verified.

Guardrail · Read-only. Product recommendations require suitability review, not a chat tool.

In-force policy summary

Every policy on one page, with the details that matter.

Insurance & Annuity ReviewInsurance & Annuities

Read-only: build one in-force summary for <client name> by combining every connected insurance source, carrier or policy-administration data and any independent policy-review or annuity-data tool. Show carrier, type, face amount or benefit, premium, term or maturity, ownership, beneficiaries and the source tool for each line, and flag any field where two sources disagree or one source has no record of a policy. Mask policy numbers to the last four characters. Do not change beneficiaries, request changes, or submit anything to a carrier.

Guardrail · Read-only. Beneficiary and ownership changes are never done from a chat tool.

Read the full connection guide →