# Travel Protection Insurance (remote · www.travelprotection.insure)

Quote US travel insurance and get a link to buy it on travelprotection.insure.

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

## Components

- remote · `www.travelprotection.insure`: 79/100 (this document), [markdown](https://verifymcp.io/servers/insure-travelprotection-travel-insurance/www.md), [page](https://verifymcp.io/servers/insure-travelprotection-travel-insurance/www)

## Channel facts

- Endpoint: `https://www.travelprotection.insure/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 74/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 is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 985 tokens (~246/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Travel Protection Insurance MCP server?

Travel Protection Insurance is a hosted endpoint at https://www.travelprotection.insure/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 insure-travelprotection-travel-insurance 'https://www.travelprotection.insure/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "insure-travelprotection-travel-insurance": {
      "url": "https://www.travelprotection.insure/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "insure-travelprotection-travel-insurance": {
      "type": "http",
      "url": "https://www.travelprotection.insure/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.insure-travelprotection-travel-insurance]
url = "https://www.travelprotection.insure/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add insure-travelprotection-travel-insurance --url 'https://www.travelprotection.insure/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  insure-travelprotection-travel-insurance:
    url: "https://www.travelprotection.insure/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "insure-travelprotection-travel-insurance": {
      "Transport": "http",
      "Url": "https://www.travelprotection.insure/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add insure-travelprotection-travel-insurance -t streamable-http -u 'https://www.travelprotection.insure/mcp'
```

### Other

```json
{
  "mcpServers": {
    "insure-travelprotection-travel-insurance": {
      "type": "http",
      "url": "https://www.travelprotection.insure/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 79, +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.

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

- [security] Tool “get_travel_insurance_coverage_details” rewrote its description, which is the text the model reads
- [cosmetic] “quote_travel_insurance” reworded the description of “departure_date”
- [cosmetic] “quote_travel_insurance” reworded the description of “return_date”
- [cosmetic] “quote_travel_insurance” reworded the description of “trip_cost”
- [cosmetic] “start_travel_insurance_checkout” reworded the description of “departure_date”
- [cosmetic] “start_travel_insurance_checkout” reworded the description of “return_date”
- [cosmetic] “start_travel_insurance_checkout” reworded the description of “trip_cost”

### 2026-10-31 (score 77, +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.

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

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

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

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

### 2026-10-24 (score 74, +1)

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

### 2026-10-22 (score 73, +1)

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

### 2026-10-20 (score 72, +1)

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

## MCP tools (4)

### `list_travel_insurance_plans` (~52 tokens)

List travel insurance plans

Lists the travel insurance plans sold by Travel Protection Insurance (www.travelprotection.insure) to US residents: each plan's price as a percentage of trip cost, main coverages and restrictions.

### `get_travel_insurance_coverage_details` (~73 tokens)

Get travel insurance coverage details

Returns the covered cancellation reasons, benefit limits and state restrictions for one plan: "standard" or "cfar" (Cancel For Any Reason). Reasons and limits follow the policy form sold in most states; policy_form_note names the states whose form differs.

Input parameters:

- `plan_id` (string, required)

### `quote_travel_insurance` (~226 tokens)

Quote travel insurance

Prices travel insurance for a trip under both plans and says whether Cancel For Any Reason (CFAR) coverage is available to this traveler, and why not when it isn't. Nothing is saved or charged.

Input parameters:

- `customer_state` (string, required): Two-letter code of the US state the traveler lives in. Only US residents can buy.
- `departure_date` (string, required): Departure date, YYYY-MM-DD. The earliest accepted is tomorrow in the traveler's home state.
- `destination` (string, required): Where the traveler is going, e.g. "Italy" or "Orlando, FL".
- `initial_payment_date` (string): Date of the traveler's first payment toward the trip, YYYY-MM-DD. Needed before payment for every plan; Cancel For Any Reason (CFAR) coverage must be bought within 14 days of it.
- `return_date` (string, required): Return date, YYYY-MM-DD, on or after departure_date and at most 110 days after it.
- `trip_cost` (number, required): Total prepaid trip cost in US dollars, up to $100,000.

### `start_travel_insurance_checkout` (~580 tokens)

Start travel insurance checkout

Creates a quote for the traveler and returns a link to finish on www.travelprotection.insure. Requires the traveler's name and email, shared only with the traveler's agreement. Home and destination address details are optional and also shared only with the traveler's agreement; when they are left out, the site asks for them before payment. Nothing is charged here. The link expires 1 hour after it is created.

Input parameters:

- `coverage_type` (string, required): The plan the traveler chose.
- `customer_address` (string): Traveler's home street address. Shared only with the traveler's agreement.
- `customer_address_2` (string): Apartment, suite or unit, if any. Shared only with the traveler's agreement.
- `customer_city` (string): Traveler's home city. Shared only with the traveler's agreement.
- `customer_email` (string, required): Where the policy documents are sent.
- `customer_first_name` (string, required): Traveler's first name.
- `customer_last_name` (string, required): Traveler's last name.
- `customer_phone` (string): Traveler's phone number. Shared only with the traveler's agreement.
- `customer_state` (string, required): Two-letter code of the US state the traveler lives in. Only US residents can buy.
- `customer_zip` (string): Traveler's home ZIP code. Shared only with the traveler's agreement.
- `departure_date` (string, required): Departure date, YYYY-MM-DD. The earliest accepted is tomorrow in the traveler's home state.
- `destination` (string, required): Where the traveler is going, e.g. "Italy" or "Orlando, FL".
- `destination_address` (string): Street address where the traveler is staying. Shared only with the traveler's agreement.
- `destination_address_2` (string): Second line of that address, if any. Shared only with the traveler's agreement.
- `destination_city` (string): City where the traveler is staying. Shared only with the traveler's agreement.
- `destination_country` (string): Two-letter country code of the destination. Shared only with the traveler's agreement.
- `destination_state` (string): State or province code where the traveler is staying; needed for US and Canadian destinations. Shared only with the traveler's agreement.
- `destination_zip` (string): Postal code where the traveler is staying. Shared only with the traveler's agreement.
- `initial_payment_date` (string): Date of the traveler's first payment toward the trip, YYYY-MM-DD. Needed before payment for every plan; Cancel For Any Reason (CFAR) coverage must be bought within 14 days of it.
- `return_date` (string, required): Return date, YYYY-MM-DD, on or after departure_date and at most 110 days after it.
- `trip_cost` (number, required): Total prepaid trip cost in US dollars, up to $100,000.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/insure-travelprotection-travel-insurance/www#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 69

## Common questions

### What is the Travel Protection Insurance MCP server?

Travel Protection Insurance is an MCP server listed in the public MCP registry as insure.travelprotection/travel-insurance. Quote US travel insurance and get a link to buy it on travelprotection.insure. This page covers its hosted endpoint (https://www.travelprotection.insure/mcp).

### Is the Travel Protection Insurance MCP server safe to use?

Travel Protection Insurance scores 79 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 Travel Protection Insurance MCP server expose?

Travel Protection Insurance exposes 4 tools: list_travel_insurance_plans, get_travel_insurance_coverage_details, quote_travel_insurance, start_travel_insurance_checkout. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.

### Does the Travel Protection Insurance MCP server require authentication?

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

### Is the Travel Protection Insurance MCP server still maintained?

Travel Protection 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://www.travelprotection.insure/mcp
- Website: https://www.travelprotection.insure/
- Changelog RSS feed: https://verifymcp.io/servers/insure-travelprotection-travel-insurance/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/insure-travelprotection-travel-insurance/www.json
- HTML version of this page: https://verifymcp.io/servers/insure-travelprotection-travel-insurance/www