Sweet Saver Fare

com.sweetsaverfarePublished by sweetsaverfare.comOfficial publisherv0.2.0Updated Oct 24, 2026

Compare observed BC Ferries fares and dates, read qualified predictions, and manage fare alerts.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server that lets an assistant compare observed BC Ferries fares and dates, read qualified predictions, and manage fare alerts.

What you can do
Compare observed BC Ferries fares and sailing dates, and read qualified fare predictions. Create and manage fare alerts so the assistant can track routes or dates of interest. Access is through a hosted remote endpoint with OAuth sign-in; no tool list is published, so exact operations are not documented.
When to use it
Useful when planning BC Ferries travel and wanting an assistant to compare observed fares across dates or keep track of price changes through alerts.
Requirements
A remote MCP endpoint at sweetsaverfare.com connected over streamable HTTP, with OAuth authentication required. No environment variables, headers or local packages are declared.
Before you install
OAuth sign-in grants the server access to your account; review the scopes requested. Alerts may involve account settings or notifications, so confirm before creating or changing them. Fare data and predictions come from a third party and should be verified before booking.

Installation

In SourceWeft

  1. Open Sweet Saver Fare in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.sweetsaverfare%2Fsweet-saver-fare/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sweet-saver-fare": {
      "type": "http",
      "url": "https://sweetsaverfare.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.