Travel Protection Insurance
REMOTE · WWW.TRAVELPROTECTION.INSURE
Quote US travel insurance and get a link to buy it on travelprotection.insure.
Available components
Last scanned (23 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% 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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 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.
- 2 Nov 26 +1
- Tool “get_travel_insurance_coverage_details” rewrote its description, which is the text the model reads security
- “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” cosmetic
- 31 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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
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 4 Nov 2026 · Probed https://www.travelprotection.insure/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.travelprotection.insure | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6583c8c4d07d27410aebe7680c980b8bbcd |
| SANs: www.travelprotection.insure | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.travelprotection.insure. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| insure. | present | 18841, 54472 | 8, 8 | Verified |
| travelprotection.insure. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.travelprotection.insure/mcp | Verified | 200 | |
| http (plaintext) | http://www.travelprotection.insure/mcp | HTTPS enforced | 301 | https://www.travelprotection.insure/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 →
get_travel_insurance_coverage_details Get travel insurance coverage details ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
No output schema declared.
No examples provided.
list_travel_insurance_plans List travel insurance plans ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_travel_insurance Quote travel insurance ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_state | string | yes | Two-letter code of the US state the traveler lives in. Only US residents can buy. |
| departure_date | string | yes | Departure date, YYYY-MM-DD. The earliest accepted is tomorrow in the traveler's home state. |
| destination | string | yes | 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 | yes | Return date, YYYY-MM-DD, on or after departure_date and at most 110 days after it. |
| trip_cost | number | yes | Total prepaid trip cost in US dollars, up to $100,000. |
No output schema declared.
No examples provided.
start_travel_insurance_checkout Start travel insurance checkout ~580
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_type | string | yes | 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 | yes | Where the policy documents are sent. |
| customer_first_name | string | yes | Traveler's first name. |
| customer_last_name | string | yes | Traveler's last name. |
| customer_phone | string | – | Traveler's phone number. Shared only with the traveler's agreement. |
| customer_state | string | yes | 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 | yes | Departure date, YYYY-MM-DD. The earliest accepted is tomorrow in the traveler's home state. |
| destination | string | yes | 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 | yes | Return date, YYYY-MM-DD, on or after departure_date and at most 110 days after it. |
| trip_cost | number | yes | Total prepaid trip cost in US dollars, up to $100,000. |
No output schema declared.
No examples provided.
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.
remote · www.travelprotection.insure
claude mcp add --transport http insure-travelprotection-travel-insurance 'https://www.travelprotection.insure/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.