Alishahi Insurance
REMOTE · ALISHAHIINSURANCE.COM
Request a home, auto, business, contractor or trucking insurance quote from a licensed broker.
Available components
Last scanned (5 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1572 tokens (~174/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “who_is_likely_to_insure” rewrote its description, which is the text the model reads security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://alishahiinsurance.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alishahiinsurance.com | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | bb4edc6ed9336b9f13facb9a88ae8128 |
| SANs: alishahiinsurance.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of alishahiinsurance.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| alishahiinsurance.com. | present | 2371 | 13 | Verified |
| alishahiinsurance.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alishahiinsurance.com/mcp | Verified | 200 | |
| http (plaintext) | http://alishahiinsurance.com/mcp | HTTPS enforced | 301 | https://alishahiinsurance.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
complete_application Add answers to an application ~126
Send the person's answers for an application Sam Alishahi started. Only send what the person told you or confirmed; leave unknown fields out. Returns the updated application with any rejected answers and why.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Answers keyed by field name from get_application. Select fields take one of their choices; dates are YYYY-MM-DD. |
| application_id | string | yes | – |
| notes | string | – | Anything else the person wants Sam to know. |
| submit | boolean | – | True when the person is done, even if optional fields are blank. |
| token | string | yes | – |
No output schema declared.
No examples provided.
find_insurance_company ~105
Look up a U.S. property and casualty insurance company by name or NAIC number in Alishahi Insurance's directory (built from state regulators' public company lists): where it is admitted (licensed), where it is an eligible surplus lines insurer, the lines it is licensed for, its premium rank by line where states publish every company, and the page to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Company name (part is fine) or 5-digit NAIC number |
No output schema declared.
No examples provided.
get_application Get an application Sam started ~71
Read a quote application Sam Alishahi started from the person's email: every field, its allowed choices, what's filled in and what's still required. The application_id and token are in Sam's reply email (Reference APP-<id>).
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
get_quote_questions Get quote questions ~55
Get the questions to ask for one coverage (names, types and allowed choices). All are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | A coverage name from list_coverages, e.g. "Homeowners" or "Tow truck". |
No output schema declared.
No examples provided.
insurance_companies_in_state ~116
List the property and casualty insurers on a state's regulator lists: admitted (licensed) companies and eligible surplus lines insurers, with NAIC numbers and licensed lines. Optional filters: status 'ad' or 'sl', and a line of business.
| Name | Type | Req | Description |
|---|---|---|---|
| line | string | – | Line of business, e.g. workers comp, homeowners, commercial auto, general liability |
| state | string | yes | Two-letter state code, e.g. TX |
| status | string | – | ad = admitted/licensed, sl = surplus lines |
No output schema declared.
No examples provided.
list_coverages List coverages ~29
List the insurance coverages Alishahi Insurance quotes, with a link to each coverage's page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_quote_request Send quote request to Sam Alishahi ~195
Send the person's quote request to Sam Alishahi, a licensed independent insurance broker, who will contact them. Only call after the person has confirmed they want to be contacted. Use real values from the person; if a field is unknown, leave it out.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | Answers keyed by question name from get_quote_questions. Select questions must use one of the listed choices. |
| contact_consent | boolean | yes | True only after the person confirmed they want Sam Alishahi to contact them about this request by phone or email. |
| coverage | string | yes | Coverage name from list_coverages. |
| string | yes | Email address. | |
| name | string | yes | Full name. |
| notes | string | – | Anything else the person wants Sam to know, such as deadlines or lender requirements. |
| phone | string | yes | Mobile phone number. |
| zip | string | – | ZIP code of the property or business. |
No output schema declared.
No examples provided.
who_is_likely_to_insure ~198
Given a plain-English description of what someone needs insured (what, where, anything unusual: claims, cancellations, age of the home or roof, the kind of business, hazards), says which insurers are likely to consider it, in order: admitted carriers that write that line in that state, then surplus lines or specialty insurers, then the state's market of last resort — each with a one-line why from the directory's evidence (licensing, premium rank, published appetite rules). Never a price or a guarantee. Ends with the next step: a quote request through Alishahi Insurance; Sam sends it to the insurers he works with that fit the risk, directly or through wholesale brokers. A company listed isn't necessarily one he is appointed with.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | yes | What they need insured, where, and the facts an underwriter would care about |
| state | string | – | Two-letter state code if known |
No output schema declared.
No examples provided.
who_writes_line_in_state ~127
Who actually writes a line of insurance in a state: companies ranked by direct premium written where the regulator publishes every company (CA, TX, IL, NC, SD, WI), otherwise the licensed companies; the directory page for the state and line is the source to cite. Use it to tell someone which insurers are real markets for their need in their state before sending a quote request.
| Name | Type | Req | Description |
|---|---|---|---|
| line | string | yes | Line of business, e.g. workers comp, homeowners, commercial auto, general liability, surety |
| state | string | yes | Two-letter state code |
No output schema declared.
No examples provided.
How do I install the Alishahi Insurance MCP server?
Alishahi Insurance is a hosted endpoint at https://alishahiinsurance.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · alishahiinsurance.com
claude mcp add --transport http com-alishahiinsurance-insurance-quotes 'https://alishahiinsurance.com/mcp'
What is the Alishahi Insurance MCP server?
Alishahi Insurance is an MCP server listed in the public MCP registry as com.alishahiinsurance/insurance-quotes. Request a home, auto, business, contractor or trucking insurance quote from a licensed broker. This page covers its hosted endpoint (https://alishahiinsurance.com/mcp).
Is the Alishahi Insurance MCP server safe to use?
Alishahi Insurance scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Alishahi Insurance MCP server expose?
Alishahi Insurance exposes 9 tools: list_coverages, get_quote_questions, submit_quote_request, find_insurance_company, insurance_companies_in_state, and 4 more. Their descriptions and schemas cost roughly 1,022 tokens of context every time the server is loaded.
Does the Alishahi Insurance MCP server require authentication?
No. We connected to Alishahi Insurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Alishahi Insurance MCP server still maintained?
Alishahi Insurance is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.