travel-insurance MCP server
io.github.HelloSafe/travel-insuranceHelloSafestreamable-httpv1.0.1Scanned
Compare travel insurance quotes from 15+ insurers — Schengen, WHV, students, long stays, seniors.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the travel-insurance MCP server can do
The travel-insurance MCP server is published by the GitHub account HelloSafe. It has 2 tools. It can create or change data (1 tool: check_card_coverage), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
check_card_coverageChecks what travel insurance a credit card already includes, from the card's own terms & conditions in HelloSafe's card database.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a bank card's travel insurance
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
Only reads 1Show 1 read-only tool
get_quoteGets travel-insurance quotes from HelloSafe for a trip: priced offers from HelloSafe partners, shown in a comparison widget.No findings
Why it is in this group
- The name "get_quote" says "get": a word for reading.
Description, as the server wrote it 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, the trip length as endDate or durationDays (not for an annual or expat cover, which runs a year), and stateResidence for a US resident. Every other field has a default. The trip length is not defaulted: a wrong length gives a wrong price. HelloSafe is a licensed insurance broker, paid a commission by the insurers whose policies it distributes.
Annotations the server declares
- title: Get travel insurance quotes
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://hellosafe.com/api/mcp-travel: tools/list returned 2 tools to an anonymous client, including check_card_coverage (write)
Posture changes
- Nov 20, 2026
- RFC 9728 protected resource metadata: https://hellosafe.com/.well-known/oauth-protected-resource to none
- Authorization servers: https://hellosafe.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: https://hellosafe.com/.well-known/oauth-protected-resource -> none; Authorization servers: https://hellosafe.com -> none; Dynamic client registration: yes -> not observed (and 1 …View diff
- RFC 9728 protected resource metadata: https://hellosafe.com/.well-known/oauth-protected-resource to none
- Authorization servers: https://hellosafe.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Tools2 changed.~2 changedView diff
- Changed:check_card_coverageChanges thingsdescriptioninputSchema
- Changed:get_quoteOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http travel-insurance https://hellosafe.com/api/mcp-travelclaude mcp add --transport http travel-insurance https://hellosafe.com/api/mcp-travelRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__travel-insurance__get_quote"
],
"ask": [
"mcp__travel-insurance__check_card_coverage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as travel-insurance. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.HelloSafe/travel-insurance/verify?hash=9bcc5556b08cf1c21b42d0c5ec1be3ee1637cf32e1838135f444210300f89044" | jq -e '.changed == false'Pinned hash 9bcc5556b08c, from Nov 15, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.HelloSafe/travel-insurance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.HelloSafe/travel-insurance)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.
travel-insurance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the travel-insurance MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the travel-insurance MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the travel-insurance MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the travel-insurance MCP server have?
- 2 tools: 1 write, 1 read. check_card_coverage and get_quote.
Does the travel-insurance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the travel-insurance MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the travel-insurance MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.