# Jerry Insurance (remote · mcp.jerry.ai)

Compare US car, home and renters insurance quotes with Jerry. Sign-in required; buy in the app.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.jerry.ai`: 69/100 (this document), [markdown](https://verifymcp.io/servers/ai-jerry-insurance/mcp.md), [page](https://verifymcp.io/servers/ai-jerry-insurance/mcp)

## Channel facts

- Endpoint: `https://mcp.jerry.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3721 tokens (~465/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Jerry Insurance MCP server?

Jerry Insurance is a hosted endpoint at https://mcp.jerry.ai/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.

### Claude

```bash
claude mcp add --transport http ai-jerry-insurance 'https://mcp.jerry.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-jerry-insurance": {
      "url": "https://mcp.jerry.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-jerry-insurance": {
      "type": "http",
      "url": "https://mcp.jerry.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-jerry-insurance]
url = "https://mcp.jerry.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-jerry-insurance": {
      "type": "remote",
      "url": "https://mcp.jerry.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-jerry-insurance --url 'https://mcp.jerry.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-jerry-insurance:
    url: "https://mcp.jerry.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-jerry-insurance": {
      "Transport": "http",
      "Url": "https://mcp.jerry.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-jerry-insurance -t streamable-http -u 'https://mcp.jerry.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-jerry-insurance": {
      "type": "http",
      "url": "https://mcp.jerry.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 64)

First indexed and scored.

## MCP tools (8)

### `jerry_get_account` (~41 tokens)

Account details

Read the name, email and phone on the customer's Jerry account, and whether the phone is verified. It doesn't verify an email or change any insurance information.

Output parameters:

- `data` (object): Customer account contact profile
- `message` (string)

### `jerry_start_shopping` (~212 tokens)

Start shopping

Start shopping for the insurance products the customer asked for. If a shopping intent for exactly these products is already open, it resumes that one. Pass the main facts you already know in application, so the status asks only for the rest. application takes the main fields only: send any other fact with jerry_update_application right after. Returns the status, with rejected and clarify. When a fact comes from anything other than the customer, sources says where, and permission holds the customer's reply allowing it.

Input parameters:

- `application` (object): The main facts the agent already knows, saved in the same call so the first status asks only for the rest. Send other facts with updateShoppingIntentApplication.
- `idempotencyKey` (string, required): Unique key for safely retrying this customer action
- `permission` (object): Required once when sources include anything but customer.
- `policyTypes` (array, required): Products to shop for.
- `sources` (array): Where these facts come from; defaults to ['customer'].

### `jerry_update_application` (~345 tokens)

Update application

Save application facts the customer gave, in their own words. Every field is optional and merges into what's saved, so send only facts that are new or changed.
\- Items with an id update that driver, car or home; items without one are added. included puts an item on the quote or leaves it off.
\- Add a car by vin, by licensePlate and licensePlateState, or by year, make and model. Send year, make and model only when there's no VIN or plate, since those set them. A final price needs the VIN.
\- Answer any other requirement in answers, by its path. A fact that has its own field here comes back rejected as typed_field if it's sent in answers.
\- coverage and history.currentMonthlyPremiumCents are optional and never block quotes. Send them only when the customer asks for a coverage level or specific coverages, or says what they pay now.
\- Drivers and cars Jerry found are in the status's suggested list, each with an id that starts with suggested:. Once the customer confirms one, send that id in drivers or vehicles with included: true.
Returns the status, with suggested. rejected lists values to correct with the customer, and clarify lists values to choose from. The rest of the write is saved either way.

Input parameters:

- `application` (object, required)
- `idempotencyKey` (string, required): Unique key for safely retrying this customer action
- `intentId` (string, required): The shopping intent id returned by an earlier shopping tool.
- `permission` (object): Required once when sources include anything but customer.
- `sources` (array): Where these facts come from; defaults to ['customer'].

### `jerry_request_quotes` (~123 tokens)

Request quotes

Request quotes. Every request needs the confirmation from the status: show its summary, get the customer's explicit yes, then pass its token and their exact reply. Nothing is requested unless requested comes back true; reason says why not, and status is the intent after the call. On stale_confirmation the facts changed: show the new confirmation and ask again.

Input parameters:

- `confirmation` (object, required)
- `idempotencyKey` (string, required): Unique key for safely retrying this customer action
- `intentId` (string, required): The shopping intent id returned by an earlier shopping tool.

### `jerry_request_final_price` (~158 tokens)

Request final price

Get the final price of the quote the customer chose. Call it first with bundleId only: that selects the quote and returns the status, which may list what the final price still needs, then a confirmation. After the customer says yes to that confirmation, call again with its token and the customer's exact reply. Nothing is requested unless requested comes back true.

Input parameters:

- `bundleId` (string, required): The bundleId of the chosen quote.
- `confirmation` (object): Omit on the first call, which selects the quote and returns the confirmation to show.
- `idempotencyKey` (string, required): Unique key for safely retrying this customer action
- `intentId` (string, required): The shopping intent id returned by an earlier shopping tool.

### `jerry_wait` (~179 tokens)

Wait for results

Wait for quotes or a final price after requesting them. Returns as soon as they're ready, or after timeoutSeconds with the status so far; call again while they're still running. When quotes are ready, it returns the quote list too. A final price is ready once it's resolved. If a Jerry agent takes it over (manual) or it's taking longer than usual (delayed), the wait stops with that reason, and the status's nextStep says what happens next. Calling again on a delayed price keeps waiting.

Input parameters:

- `for` (string, required): quotes after jerry_request_quotes; final_price after jerry_request_final_price requested it.
- `intentId` (string, required): The shopping intent id returned by an earlier shopping tool.
- `timeoutSeconds` (integer): Longest time to wait, in seconds; default 20, at most 20.

### `jerry_get_status` (~119 tokens)

Shopping status

Read where the customer's insurance shopping stands: the stage, what the current goal still needs (by application path), a summary of the application, what Jerry found that isn't on the application yet (suggested) and, when a request is ready, the confirmation to show. It doesn't change anything.

Input parameters:

- `full` (boolean): Include every typed application fact by application path, with sensitive values masked.
- `intentId` (string): The shopping intent id returned by an earlier shopping tool. Omit it to read the customer's most recent open intent.

### `jerry_get_quotes` (~135 tokens)

View quotes

List every quote for a shopping intent, cheapest first by monthly price (in USD cents); each policy has a coverageSummary. Pass up to 4 bundleIds to also get their coverages, discounts and payment plans, for example to compare them. Prices are estimates until priceStatus is final. Declined quotes are left out and counted in declinedCount. It doesn't request quotes.

Input parameters:

- `bundleIds` (array): Up to 4 bundle ids to return with coverages, discounts and payment plans. Omit to list every quote.
- `intentId` (string, required): The shopping intent id returned by an earlier shopping tool.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-jerry-insurance/mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 67
- 2026-10-29: 66
- 2026-10-28: 66
- 2026-10-27: 65
- 2026-10-26: 65
- 2026-10-25: 64

## Common questions

### What is the Jerry Insurance MCP server?

Jerry Insurance is an MCP server listed in the public MCP registry as ai.jerry/insurance. Compare US car, home and renters insurance quotes with Jerry. Sign-in required; buy in the app. This page covers its hosted endpoint (https://mcp.jerry.ai/mcp).

### Is the Jerry Insurance MCP server safe to use?

Jerry Insurance scores 69 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 Jerry Insurance MCP server expose?

Jerry Insurance exposes 8 tools: jerry_get_account, jerry_start_shopping, jerry_update_application, jerry_request_quotes, jerry_request_final_price, and 3 more. Their descriptions and schemas cost roughly 1,312 tokens of context every time the server is loaded.

### Does the Jerry Insurance MCP server require authentication?

No. We connected to Jerry Insurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Jerry Insurance MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.jerry.ai/mcp
- Website: https://mcp.jerry.ai/docs
- Changelog RSS feed: https://verifymcp.io/servers/ai-jerry-insurance/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-jerry-insurance/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-jerry-insurance/mcp