io.github.Fabsbags/swisstrip-mcp
REMOTE · MCP.SWISSTRIP.APP · 2 COMPONENTS
Canonical SwissTrip MCP — independent SBB/CFF/FFS schedules, prices, and ticket links by SwissTrip.
Available components
Last scanned (12 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 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
- 13 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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 0
- Stability: 0.97 → pass security
- 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
- 30 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
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://mcp.swisstrip.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=swisstrip.app | CN=YE1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 52db3c867648c9160fe6cb1fa3f26404b60 |
| SANs: *.swisstrip.app, swisstrip.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.swisstrip.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| swisstrip.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.swisstrip.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://mcp.swisstrip.app/mcp | HTTPS enforced | 301 | https://mcp.swisstrip.app/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 →
get_more_connections Get More Connections ~63
Load earlier or later train connections for a previous search. Use the collection ID from search_connections results.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | string | yes | Collection ID from search_connections results |
| direction | string | yes | "next" for later trains, "previous" for earlier trains |
No output schema declared.
No examples provided.
get_prices Get Prices ~125
Get ticket prices in CHF for one or more train connections. Supports Half-Fare card (Halbtax) and GA travelcard discounts. Up to 10 trip_ids per call — batch them in a single request rather than calling once per connection. Use trip_ids from a recent search_connections result; do not invent IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| reduction_card | string | – | Swiss reduction card: HALF_FARE (Halbtax), GA (General Abonnement), or NONE |
| traveler_type | string | – | Traveler type |
| trip_ids | array | yes | Trip IDs from search_connections results |
No output schema declared.
No examples provided.
get_ticket_link Get Ticket Link ~208
Get a direct purchase link to buy a train ticket on SBB.ch. Only call this when the user wants to buy a specific ticket. On mobile with SBB app installed, opens directly in the app with Halbtax/GA applied automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Travel date YYYY-MM-DD |
| from_id | string | yes | Origin station ID (e.g. "8503000") |
| from_name | string | yes | Origin station name (e.g. "Zürich HB") |
| reduction_card | string | – | Swiss reduction card: HALF_FARE (Halbtax), GA (General Abonnement), or NONE |
| time | string | yes | Departure time HH:MM |
| to_id | string | yes | Destination station ID (e.g. "8507000") |
| to_name | string | yes | Destination station name (e.g. "Bern") |
| traveler_type | string | – | Traveler type |
| trip_id | string | yes | Trip ID to purchase |
No output schema declared.
No examples provided.
get_trip_details Get Trip Details ~50
Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_id | string | yes | Trip ID from search_connections results |
No output schema declared.
No examples provided.
search_connections Search Connections ~277
Find train connections between two Swiss stations. Accepts station names directly (e.g. "Zürich HB", "Bern") or UIC IDs — name resolution happens internally. Returns live schedules with departure/arrival times, duration, transfers, and trip IDs for downstream pricing/details/ticket calls. Live data: includes delays and cancellations for trains departing within 30 min.
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_time | boolean | – | Defaults to false (treat `time` as departure). Only set true when the user EXPLICITLY says they want to ARRIVE by a specific time ("I need to be in Bern by 9am", "arriving at 14:00"). For loose phras… |
| date | string | – | Travel date in YYYY-MM-DD format (default: today) |
| from | string | yes | Origin station name or ID (e.g. "Zurich HB" or "8503000") |
| time | string | – | Time in HH:MM (Europe/Zurich local time, 24h). By default treated as DEPARTURE time. Default: now. |
| to | string | yes | Destination station name or ID (e.g. "Bern" or "8507000") |
No output schema declared.
No examples provided.
search_stations Search Stations ~120
Search for Swiss train stations, addresses, or points of interest by name. Returns UIC station IDs (e.g. "8503000" for Zürich HB) used by the other tools. Note: search_connections accepts station names directly, so this tool is only needed when the user explicitly asks for station info or when you need disambiguation between multiple matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results |
| query | string | yes | Station name to search for (e.g. "Zurich", "Bern", "Interlaken") |
No output schema declared.
No examples provided.
How do I install the io.github.Fabsbags/swisstrip-mcp server?
io.github.Fabsbags/swisstrip-mcp is a hosted endpoint at https://mcp.swisstrip.app/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 · mcp.swisstrip.app
claude mcp add --transport http fabsbags-swisstrip-mcp 'https://mcp.swisstrip.app/mcp'
What is the io.github.Fabsbags/swisstrip-mcp server?
io.github.Fabsbags/swisstrip-mcp is listed in the public MCP registry as io.github.Fabsbags/swisstrip-mcp. Canonical SwissTrip MCP, independent SBB/CFF/FFS schedules, prices, and ticket links by SwissTrip. This page covers its hosted endpoint (https://mcp.swisstrip.app/mcp).
Is the io.github.Fabsbags/swisstrip-mcp server safe to use?
io.github.Fabsbags/swisstrip-mcp scores 23 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.Fabsbags/swisstrip-mcp server expose?
io.github.Fabsbags/swisstrip-mcp exposes 6 tools: search_stations, search_connections, get_trip_details, get_more_connections, get_prices, get_ticket_link. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.
Does the io.github.Fabsbags/swisstrip-mcp server require authentication?
Its publisher declares no required credentials for io.github.Fabsbags/swisstrip-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.Fabsbags/swisstrip-mcp server still maintained?
io.github.Fabsbags/swisstrip-mcp 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.