Global TripX
REMOTE · GLOBALTRIPX.COM
Travel answers from Global TripX: entry checks for 199 countries, weather, packing, safety.
Available components
Last scanned (19 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security77
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 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 Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 429 tokens (~143/item across 3 items; 3 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Probed https://globaltripx.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=globaltripx.com | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 60e32fbad281d0201352c722df8862d4 |
| SANs: globaltripx.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 globaltripx.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| globaltripx.com. | DS published | 2371 | 13 | Verified |
| globaltripx.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://globaltripx.com/mcp | Verified | 200 | |
| http (plaintext) | http://globaltripx.com/mcp | HTTPS enforced | 301 | https://globaltripx.com/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 →
ask_tripx Ask the Global TripX travel helper ~117
Answer a travel question (destination, season, what to pack, entry rules, money, safety, food, airports) using only Global TripX guides, in Korean, English or Japanese. Returns a short answer plus the source pages. Covers 199 countries entry checks and 43,000+ places. Use it for trips from or to Korea and Japan especially.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Answer language: ko, en or ja (default: guessed from the question) |
| question | string | yes | The traveller question, any language |
No output schema declared.
No examples provided.
country_entry_check Before-you-fly check for a country ~113
Get the Global TripX before-departure page for a country (entry/visa notes, travel advisories, health notes from Korean public data). Give a country name in any language.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Destination country name in any language (e.g. "Vietnam", "베트남", "ベトナム") |
| lang | string | – | Language of the page: ko, en or ja (default: guessed from the country name). The 199-country check page is fullest in ko. |
No output schema declared.
No examples provided.
search_tripx_guides Search Global TripX guides ~133
Search Global TripX travel guides and tools (destination hubs, trip checklists, weather by month, safety numbers, food, holiday planner, airport tips). Returns titles, one-line summaries and links.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the guides to search: ko, en or ja (default: guessed from the query) |
| limit | integer | – | How many results to return, 1-10 (default 5) |
| query | string | yes | What to look for, any language (e.g. "Sapporo December packing", "오사카 아이랑", "台湾 SIM") |
No output schema declared.
No examples provided.
How do I install the Global TripX MCP server?
Global TripX is a hosted endpoint at https://globaltripx.com/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 · globaltripx.com
claude mcp add --transport http com-globaltripx-tripx 'https://globaltripx.com/mcp'
What is the Global TripX MCP server?
Global TripX is an MCP server listed in the public MCP registry as com.globaltripx/tripx. Travel answers from Global TripX: entry checks for 199 countries, weather, packing, safety. This page covers its hosted endpoint (https://globaltripx.com/mcp).
Is the Global TripX MCP server safe to use?
Global TripX scores 75 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 Global TripX MCP server expose?
Global TripX exposes 3 tools: ask_tripx, search_tripx_guides, country_entry_check. Their descriptions and schemas cost roughly 363 tokens of context every time the server is loaded.
Does the Global TripX MCP server require authentication?
No. We connected to Global TripX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Global TripX MCP server still maintained?
Global TripX is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Global TripX MCP server?
VerifyMCP ran 13 checks on Global TripX, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.