Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.HelloSafe/travel-insurance

REMOTE · HELLOSAFE.COM · SCANNED SEP 20

Compare travel insurance quotes from 15+ insurers — Schengen, WHV, students, long stays, seniors.

Available components

remote · hellosafe.com 77
0 this week 77 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability57
  • 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 701 tokens (~175/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
Install

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

# add to Claude Code
claude mcp add --transport http hellosafe-travel-insurance 'https://hellosafe.com/api/mcp-travel'
// .cursor/mcp.json
{
  "mcpServers": {
    "hellosafe-travel-insurance": {
      "url": "https://hellosafe.com/api/mcp-travel"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hellosafe-travel-insurance": {
      "type": "http",
      "url": "https://hellosafe.com/api/mcp-travel"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.hellosafe-travel-insurance]
url = "https://hellosafe.com/api/mcp-travel"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hellosafe-travel-insurance": {
      "type": "remote",
      "url": "https://hellosafe.com/api/mcp-travel",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hellosafe-travel-insurance --url 'https://hellosafe.com/api/mcp-travel' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  hellosafe-travel-insurance:
    url: "https://hellosafe.com/api/mcp-travel"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hellosafe-travel-insurance": {
      "Transport": "http",
      "Url": "https://hellosafe.com/api/mcp-travel"
    }
  }
}
# add to Vellum
assistant mcp add hellosafe-travel-insurance -t streamable-http -u 'https://hellosafe.com/api/mcp-travel'
// mcp.json
{
  "mcpServers": {
    "hellosafe-travel-insurance": {
      "type": "http",
      "url": "https://hellosafe.com/api/mcp-travel"
    }
  }
}

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

Changelog

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.

  • 9 Sept 26 −1

    No change was recorded against any check on this day. Schema Quality & AI Usability went from 61 to 57.

  • 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
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

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

  • 11 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
  • 31 Jul 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
Diagnostics

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 20 Sept 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 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA256 a35cd955aea9f2a10eb8446435827b96
SANs: hellosafe.com, hellotravel-sea-dashboard.hellosafe.com, *.hellotravel-sea-dashboard.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 insecure

Validation of hellosafe.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
hellosafe.com. 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
Header Value
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 Inconclusive 405
MCP tools · 2 exposed · ~662 tokens

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 →

Tool Tokens
check_card_coverage ~355

Use HelloSafe to check what travel insurance a credit card already includes, from the card's real terms & conditions. Call whenever the user asks what their card covers for a trip (medical, cancellation, baggage, ski…), whether their card is enough, or mentions relying on their card's insurance. Identify the card from its name (and bank / country when given). Returns the real covered guarantees with amounts and conditions, plus the coverage gaps for the trip. If gaps exist, offer to get complementary travel-insurance quotes via get_quote, passing this card's id as `cardId` so the offers are ranked by how well they fill the gaps. Never invent coverage: only state what this tool returns.

NameTypeReqDescription
bankCountrystring–ISO-2 country of the issuing bank (e.g. "US", "FR"). Defaults to the user's country of residence when known — greatly improves matching.
cardIdnumber–Exact HelloSafe card ID from a previous call — use it to re-check a specific candidate instead of fuzzy matching.
cardQuerystring–Card name as the user said it, expanded ("American Express Platinum", not "Amex Plat"). Include the bank when known ("Chase Sapphire Reserve"). Omit only when cardId is provided.
localestring–Language the user is conversing in, as a BCP 47 tag or 2-letter code (e.g. "fr", "pt-BR"). ALWAYS pass it.
networkstring–Card network when stated: "Visa", "Mastercard", "Amex".
tripContextobject–Optional trip details — sharpen the gap analysis. Omit what you do not know.
NameTypeReqDescription
_assistantGuidanceobject––
allGuaranteesarray–The card's FULL guarantee sheet, grouped by section (travel first) — render as one markdown table per section: Guarantee | Your card | Recommended | Verdict.
alternativesarray–Other cards matching the query. If the analysed card is not the user's, ask which one and call again with its cardId.
cancellationOnlyGapboolean–True when cancellation is the ONLY gap — suggest a cancellation-only policy (intent "cancellation" in get_quote), usually much cheaper.
cardobject–The card the analysis is about.
coveredarray–Travel guarantees the card really includes, with amounts and conditions from the card T&Cs.
errorstring–Human-readable reason when the check could not run. Absent on success.
gapsarray–Guarantees missing or insufficient for the trip — the offer features a complementary policy should provide.
unknownarray–Core guarantees with no data on this card — phrase as "not documented, check your contract", never as "not covered".

No examples provided.

get_quote ~307

Use HelloSafe to get travel-insurance quotes whenever the user wants travel insurance. Returns priced offers from HelloSafe partners and renders the comparison widget. Required: countryResidence, arrivalCountries, traveller age(s). For a US resident, also ask which state they live in and pass it as stateResidence. Everything else has a sensible default — never ask the user for an optional field. After calling, reply with 1-2 short sentences highlighting the recommended offer — never re-list offers as a table, never paste subscribe URLs.

NameTypeReqDescription
cardIdnumber–HelloSafe card ID returned by check_card_coverage. Pass it when the user holds a credit card with travel cover: offers are then re-ranked by how well they fill that card's coverage gaps, and each off…
displayCurrencystring–ISO 4217 code to override the widget display currency. Omit unless the user explicitly asked for a different display currency than the trip-cost currency.
localestring–Language the user is conversing in, as a BCP 47 tag or 2-letter code (e.g. "fr", "pt-BR"). ALWAYS pass it — the widget and all offer texts are localized with it. Falls back to the ChatGPT account loc…
subscriptionIdstring–Existing subscription ID to update instead of creating a new one.
tripInfoobjectyesTrip details.
NameTypeReqDescription
_assistantGuidanceobject–Guidance for the assistant reply — follow "instruction".
cardContextobject–Present only when the quote was computed against a card (cardId argument): the card and its gaps.
displayOffersarray–Priced offers sorted by price, with the recommended offer (isBestScore=true) promoted first.
errorstring–Human-readable reason when the quote could not be generated. Absent on success.
subscribeUrlstring–HelloSafe comparator URL for this quote. The widget already renders clickable buttons — never paste it in the reply.
subscriptionIdstring–Quote session ID — pass it back as `subscriptionId` to update this quote instead of creating a new one.
translationsobject–Localized UI strings consumed by the widget — not meant for the assistant.
tripInfoobject–Normalized trip parameters the quote was computed with.

No examples provided.

Common questions

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 77 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 662 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.