_ registry / mcp streamable-http · checked 1h ago

alishahi-insurance

https://alishahiinsurance.com

Registry code: ba6670e8eee53529

api record

Alishahi Insurance is an independent insurance broker in Beverly Hills, California (Sam Alishahi, CA License #4348151). It shops home, auto, business, contractor, trucking, professional and specialty coverage across many insurance companies, directly and through wholesale markets, and takes requests from every state. A quote request is reviewed personally by Sam, who follows up by phone or email; no price is given and no coverage is bound until confirmed in writing. To request a quote: call list_coverages to find the right coverage, get_quote_questions to see what to ask, ask the person the…

endpoint
https://alishahiinsurance.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is alishahi-insurance live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is alishahi-insurance free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does alishahi-insurance have?
5 tools: get_quote_questions, submit_quote_request, complete_application, list_coverages, get_application.
Is alishahi-insurance safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
205ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open1 auth-required 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_coverages open 1h ago

    List the insurance coverages Alishahi Insurance quotes, with a link to each coverage's page.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_application auth-required 1h ago

    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>).

    mcp-tool

    {
      "type": "object",
      "required": [
        "application_id",
        "token"
      ],
      "properties": {
        "token": {
          "type": "string"
        },
        "application_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • get_quote_questions unknown 1h ago

    Get the questions to ask for one coverage (names, types and allowed choices). All are optional.

    mcp-tool

    {
      "type": "object",
      "required": [
        "coverage"
      ],
      "properties": {
        "coverage": {
          "type": "string",
          "description": "A coverage name from list_coverages, e.g. \"Homeowners\" or \"Tow truck\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • submit_quote_request unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "coverage",
        "name",
        "phone",
        "email",
        "contact_consent"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "ZIP code of the property or business."
        },
        "name": {
          "type": "string",
          "description": "Full name."
        },
        "email": {
          "type": "string",
          "description": "Email address."
        },
        "notes": {
          "type": "string",
          "description": "Anything else the person wants Sam to know, such as deadlines or lender requirements."
        },
        "phone": {
          "type": "string",
          "description": "Mobile phone number."
        },
        "answers": {
          "type": "object",
          "description": "Answers keyed by question name from get_quote_questions. Select questions must use one of the listed choices.",
          "additionalProperties": {
            "type": "string"
          }
        },
        "coverage": {
          "type": "string",
          "description": "Coverage name from list_coverages."
        },
        "contact_consent": {
          "type": "boolean",
          "description": "True only after the person confirmed they want Sam Alishahi to contact them about this request by phone or email."
        }
      },
      "additionalProperties": false
    }
    arguments 48 lines
  • complete_application unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "application_id",
        "token",
        "answers"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "description": "Anything else the person wants Sam to know."
        },
        "token": {
          "type": "string"
        },
        "submit": {
          "type": "boolean",
          "description": "True when the person is done, even if optional fields are blank."
        },
        "answers": {
          "type": "object",
          "description": "Answers keyed by field name from get_application. Select fields take one of their choices; dates are YYYY-MM-DD.",
          "additionalProperties": {
            "type": "string"
          }
        },
        "application_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ba6670e8eee53529.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ba6670e8eee53529/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ba6670e8eee53529/badge.svg)](https://brick.blue/agent/ba6670e8eee53529?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.