io.github.HelloSafe/travel-insurance
REMOTE · HELLOSAFE.COM
Compare travel insurance quotes from 15+ insurers — Schengen, WHV, students, long stays, seniors.
Available components
Last scanned (9 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 Usability54
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 897 tokens (~224/item across 4 items; 2 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
- Supports UI / widget rendering.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 +8
- HTTPS: unverified → pass ▲ security
- DNSSEC: fail → pass ▲ security
- HSTS header: fail → pass ▲ security
- Tool “check_card_coverage” rewrote its description, which is the text the model reads security
- Tool “get_quote” rewrote its description, which is the text the model reads security
- “check_card_coverage” reworded the description of “cardId” cosmetic
- “check_card_coverage” reworded the description of “cardQuery” cosmetic
- “check_card_coverage” reworded the description of “locale” cosmetic
- “check_card_coverage” reworded the description of “tripContext” cosmetic
- “get_quote” reworded the description of “cancelForAnyReason” cosmetic
- “get_quote” reworded the description of “cardId” cosmetic
- “get_quote” reworded the description of “displayCurrency” cosmetic
- “get_quote” reworded the description of “locale” cosmetic
- “get_quote” reworded the description of “requiredCoverages” cosmetic
- 13 Oct 26 −1
- Schema quality: 173 → 240 ▼ functional
- “get_quote” added an optional parameter “cancelForAnyReason” cosmetic
- “get_quote” added an optional parameter “requiredCoverages” cosmetic
- 10 Oct 26 +1
No change was recorded against any check on this day. Schema Quality & AI Usability went from 57 to 59.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Tool “get_quote” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 5 Sept 26 0
- Tool “get_quote” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool “get_quote” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- New tool “check_card_coverage” functional
- “get_quote” added an optional parameter “cardId” cosmetic
- “get_quote” reworded the description of “locale” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://hellosafe.com/api/mcp-travel
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hellosafe.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2f2aafb74d8479180e3ed454d0f657cd |
| SANs: hellosafe.com, reporting.hellosafe.com, *.reporting.hellosafe.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 hellosafe.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hellosafe.com. | present | 2371 | 13 | Verified |
| hellosafe.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=86400 |
| content-security-policy | frame-ancestors 'self' |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hellosafe.com/api/mcp-travel | Verified | 200 | |
| http (plaintext) | http://hellosafe.com/api/mcp-travel | HTTPS enforced | 301 | https://hellosafe.com/api/mcp-travel |
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 →
check_card_coverage Check a bank card's travel insurance ~329
Checks what travel insurance a credit card already includes, from the card's own terms & conditions in HelloSafe's card database. For questions about what a card covers for travel (medical, cancellation, baggage, ski…) or whether it is enough for a trip. The card is identified from its name (and bank / country when given). Returns the covered guarantees with amounts and conditions, the coverage gaps, and the card id, which get_quote accepts as `cardId` to rank offers by how well they fill those gaps. Coverage comes from the card's terms only: anything not returned is not documented.
| Name | Type | Req | Description |
|---|---|---|---|
| bankCountry | string | – | ISO-2 country of the issuing bank (e.g. "US", "FR"). Defaults to the user's country of residence when known — greatly improves matching. |
| cardId | number | – | Exact HelloSafe card ID from a previous call: it re-checks that card instead of matching by name. |
| cardQuery | string | – | Card name as the user said it, expanded ("American Express Platinum", not "Amex Plat"), with the bank when known ("Chase Sapphire Reserve"). Not needed when cardId is given. |
| locale | string | – | Language the user is conversing in, as a BCP 47 tag or 2-letter code (e.g. "fr", "pt-BR"). Guarantee labels are localized with it. |
| network | string | – | Card network when stated: "Visa", "Mastercard", "Amex". |
| tripContext | object | – | Optional trip details; they sharpen the gap analysis. |
| Name | Type | Req | Description |
|---|---|---|---|
| _assistantGuidance | object | – | Context of the result: what the widget shows and the facts behind the analysis. |
| allGuarantees | array | – | The card's FULL guarantee sheet, grouped by section (travel first). Shown in the widget. |
| alternatives | array | – | Other cards matching the query; any of their ids can be passed back as cardId. |
| cancellationOnlyGap | boolean | – | True when cancellation is the ONLY gap: a cancellation-only policy (get_quote intent "cancellation") is then usually much cheaper than full cover. |
| card | object | – | The card the analysis is about. |
| cardWidget | object | – | Data rendered by the card widget (gaps, catches, full sheet) — not meant for the assistant. |
| covered | array | – | Travel guarantees the card really includes, with amounts and conditions from the card T&Cs. |
| error | string | – | Human-readable reason when the check could not run. Absent on success. |
| gaps | array | – | Guarantees missing or insufficient for the trip — the offer features a complementary policy should provide. |
| translations | object | – | Localized UI strings consumed by the widget — not meant for the assistant. |
| unknown | array | – | Core guarantees with no data on this card: not documented in HelloSafe's data, which is not the same as not covered. |
No examples provided.
get_quote Get travel insurance quotes ~529
Gets travel-insurance quotes from HelloSafe for a trip: priced offers from HelloSafe partners, shown in a comparison widget. Required: countryResidence, arrivalCountries (not for an annual multi-trip cover, which is worldwide), traveller ages, and stateResidence for a US resident. Every other field has a default. HelloSafe is a licensed insurance broker, paid a commission by the insurers whose policies it distributes.
| Name | Type | Req | Description |
|---|---|---|---|
| cancelForAnyReason | boolean | – | Cancel For Any Reason option, like trip cancellation: an add-on bought with the policy (extra cost, a purchase window counted from the first trip payment, usually 75 % of prepaid costs refunded). Sol… |
| cardId | number | – | HelloSafe card ID returned by check_card_coverage, for a user who holds a credit card with travel cover: offers are then re-ranked by how well they fill that card's coverage gaps, and each offer list… |
| displayCurrency | string | – | ISO 4217 code of a display currency other than the trip-cost currency. Without it, amounts are shown in the trip-cost currency. |
| locale | string | – | Language the user is conversing in, as a BCP 47 tag or 2-letter code (e.g. "fr", "pt-BR"). The widget and all offer texts are localized with it; without it, the language the assistant app sends is us… |
| requiredCoverages | array | – | Optional filter on policy features, the guarantee filters of the HelloSafe comparison site: only the offers whose contract includes every listed cover are returned, that cover listed first. maternity… |
| subscriptionId | string | – | Existing subscription ID to update instead of creating a new one. |
| tripInfo | object | yes | Trip details. |
| Name | Type | Req | Description |
|---|---|---|---|
| _assistantGuidance | object | – | Context of the result: what the widget already shows, how offers were ranked, and a summary of the recommended offer. |
| cardContext | object | – | Present only when the quote was computed against a card (cardId argument): the card and its gaps. |
| displayOffers | array | – | Priced offers sorted by price, with the recommended offer (isBestScore=true) promoted first. |
| error | string | – | Human-readable reason when the quote could not be generated. Absent on success. |
| subscribeUrl | string | – | HelloSafe comparator URL for this quote, where the user compares and buys. The widget shows it as a button on each offer. |
| subscriptionId | string | – | Quote session ID; sent back as `subscriptionId`, it updates this quote instead of creating a new one. |
| translations | object | – | Localized UI strings consumed by the widget — not meant for the assistant. |
| tripInfo | object | – | Normalized trip parameters the quote was computed with. |
No examples provided.
How do I install the io.github.HelloSafe/travel-insurance MCP server?
io.github.HelloSafe/travel-insurance is a hosted endpoint at https://hellosafe.com/api/mcp-travel, 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 · hellosafe.com
claude mcp add --transport http hellosafe-travel-insurance 'https://hellosafe.com/api/mcp-travel'
What is the io.github.HelloSafe/travel-insurance MCP server?
io.github.HelloSafe/travel-insurance is an MCP server listed in the public MCP registry as io.github.HelloSafe/travel-insurance. Compare travel insurance quotes from 15+ insurers, Schengen, WHV, students, long stays, seniors. This page covers its hosted endpoint (https://hellosafe.com/api/mcp-travel).
Is the io.github.HelloSafe/travel-insurance MCP server safe to use?
io.github.HelloSafe/travel-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 io.github.HelloSafe/travel-insurance MCP server expose?
io.github.HelloSafe/travel-insurance exposes 2 tools: get_quote, check_card_coverage. Their descriptions and schemas cost roughly 858 tokens of context every time the server is loaded.
Does the io.github.HelloSafe/travel-insurance MCP server require authentication?
No. We connected to io.github.HelloSafe/travel-insurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.HelloSafe/travel-insurance MCP server still maintained?
io.github.HelloSafe/travel-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.