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

io.github.Fabsbags/swisstrip-mcp

REMOTE · MCP.SWISSTRIP.APP · 2 COMPONENTS · SCANNED AUG 3

Canonical SwissTrip MCP — independent SBB/CFF/FFS schedules, prices, and ticket links by SwissTrip.

+5 this week 76 Trust /100
Trust breakdown (6 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 →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 952 tokens (~86/item across 11 items; 6 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.swisstrip.app

# add to Claude Code
claude mcp add --transport http fabsbags-swisstrip-mcp https://mcp.swisstrip.app/mcp
# ~/.codex/config.toml
[mcp_servers.fabsbags-swisstrip-mcp]
url = "https://mcp.swisstrip.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fabsbags-swisstrip-mcp": {
      "type": "remote",
      "url": "https://mcp.swisstrip.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fabsbags-swisstrip-mcp --url https://mcp.swisstrip.app/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fabsbags-swisstrip-mcp:
    url: "https://mcp.swisstrip.app/mcp"
// mcp.json
{
  "mcpServers": {
    "fabsbags-swisstrip-mcp": {
      "type": "http",
      "url": "https://mcp.swisstrip.app/mcp"
    }
  }
}

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.

  • 2 Aug 26 +1

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

  • 31 Jul 26 +2
    • 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
  • 29 Jul 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.

  • 28 Jul 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.

  • 27 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
  • 26 Jul 26 71

    First indexed and scored.

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 3 Aug 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 11 Jul 2026 9 Oct 2026 ECDSA 256 ECDSA-SHA384 5695ab20628ef7003c313d49329531163fd
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
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 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
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.swisstrip.app/mcp Verified 200
http (plaintext) http://mcp.swisstrip.app/mcp HTTPS enforced 301 https://mcp.swisstrip.app/mcp
MCP tools — 6 exposed · ~843 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.

Tool Tokens
get_more_connections ~63

Load earlier or later train connections for a previous search. Use the collection ID from search_connections results.

NameTypeReqDescription
collection_idstringyesCollection ID from search_connections results
directionstringyes"next" for later trains, "previous" for earlier trains

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
reduction_cardstringSwiss reduction card: HALF_FARE (Halbtax), GA (General Abonnement), or NONE
traveler_typestringTraveler type
trip_idsarrayyesTrip IDs from search_connections results

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
datestringyesTravel date YYYY-MM-DD
from_idstringyesOrigin station ID (e.g. "8503000")
from_namestringyesOrigin station name (e.g. "Zürich HB")
reduction_cardstringSwiss reduction card: HALF_FARE (Halbtax), GA (General Abonnement), or NONE
timestringyesDeparture time HH:MM
to_idstringyesDestination station ID (e.g. "8507000")
to_namestringyesDestination station name (e.g. "Bern")
traveler_typestringTraveler type
trip_idstringyesTrip ID to purchase

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
trip_idstringyesTrip ID from search_connections results

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
arrival_timebooleanDefaults 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…
datestringTravel date in YYYY-MM-DD format (default: today)
fromstringyesOrigin station name or ID (e.g. "Zurich HB" or "8503000")
timestringTime in HH:MM (Europe/Zurich local time, 24h). By default treated as DEPARTURE time. Default: now.
tostringyesDestination station name or ID (e.g. "Bern" or "8507000")

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
limitnumberMaximum number of results
querystringyesStation name to search for (e.g. "Zurich", "Bern", "Interlaken")

No output schema declared.

No examples provided.