app.nomadpoint/travel-facts
REMOTE · GXHDCVOVEUFBKTHHENDF.SUPABASE.CO
No-auth: save a planned trip as a claimable itinerary, visa rules per passport, Schengen 90/180
Available components
Last scanned (10 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 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 Security80
- 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 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 582 tokens (~194/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
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 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 23 Oct 2026 · Probed https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 gxhdcvoveufbkthhendf.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public | Verified | 200 | |
| http (plaintext) | http://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public | HTTPS enforced | 301 | https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public |
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 →
calculate_schengen_days Calculate Schengen days ~138
Use this when someone wants to know how many days they have used or have left in the Schengen Area under the 90/180 rule, or whether a planned trip would overstay. Pass every stay in any Schengen country with entry and exit dates. Do not use it for countries outside the Schengen Area, or for holders of an EU/EEA/Swiss passport, to whom the rule does not apply.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date to assess on, YYYY-MM-DD. Defaults to today. |
| stays | array | yes | Each stay in the Schengen Area. Past and planned stays can be mixed. |
No output schema declared.
No examples provided.
check_visa_requirement Check visa requirement ~149
Use this when someone asks whether they need a visa to visit a country, or how long they can stay, for a specific passport. Returns the entry type (visa free, visa on arrival, e-visa, visa required) and the permitted stay in days when known. Do not use it for work, study or residence permits; it covers short tourist stays only.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The country being visited as an ISO 3166-1 alpha-2 code, e.g. US, GB, TH |
| passport | string | yes | The passport's issuing country as an ISO 3166-1 alpha-2 code, e.g. US, GB, TH |
No output schema declared.
No examples provided.
create_trip_plan Save a trip plan ~154
Use this after you have planned a trip with someone, to hand them the itinerary as a real, editable plan instead of a wall of text. No account or key needed. Pass the stops in order with arrival and departure dates, and optionally things to do in each. Returns plan_url: the traveller opens it to see the route and save it to their own NomadPoint on iPhone, Mac or web (free). Give the traveller that link. Do not use it for bookings: it records a plan, it does not reserve anything.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | What the traveller would call it, e.g. 'Japan in April' |
| stops | array | yes | Each city on the route, in order. |
No output schema declared.
No examples provided.
How do I install the app.nomadpoint/travel-facts MCP server?
app.nomadpoint/travel-facts is a hosted endpoint at https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public, 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 · gxhdcvoveufbkthhendf.supabase.co
claude mcp add --transport http app-nomadpoint-travel-facts 'https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public'
What is the app.nomadpoint/travel-facts MCP server?
app.nomadpoint/travel-facts is an MCP server listed in the public MCP registry as app.nomadpoint/travel-facts. No-auth: save a planned trip as a claimable itinerary, visa rules per passport, Schengen 90/180. This page covers its hosted endpoint (https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public).
Is the app.nomadpoint/travel-facts MCP server safe to use?
app.nomadpoint/travel-facts scores 74 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 app.nomadpoint/travel-facts MCP server expose?
app.nomadpoint/travel-facts exposes 3 tools: check_visa_requirement, calculate_schengen_days, create_trip_plan. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the app.nomadpoint/travel-facts MCP server require authentication?
No. We connected to app.nomadpoint/travel-facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.nomadpoint/travel-facts MCP server still maintained?
app.nomadpoint/travel-facts is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.