Tasters

ch.tastersPublished by tasters.chOfficial publisherv0.4.0Updated Nov 4, 2026

Swiss wine shop: food pairings, in-stock wines with CHF prices, your cellar. Ships to Switzerland.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Swiss wine shop MCP server that lets an assistant suggest food pairings, check in-stock wines with CHF prices, and view your cellar.

What you can do
  • Suggest wine pairings for food.
  • Look up wines that are in stock, with prices in CHF.
  • View and work with your own wine cellar.
  • Connect through a hosted remote endpoint with OAuth sign-in.
When to use it
Useful when you want an assistant to recommend wines for a meal, check availability and Swiss prices, or consult your stored cellar while planning food and drink.
Requirements
A remote MCP endpoint at the provider's site; no local install or package. OAuth authentication is required, so you need a Tasters account to sign in. Ships to Switzerland.
Before you install
Sign-in grants the server access to your account and cellar data through OAuth; review the scopes requested. Wine prices and availability come from the shop and may change. Delivery is limited to Switzerland.

Installation

In SourceWeft

  1. Open Tasters 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/ch.tasters%2Fmcp/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": {
    "tasters": {
      "type": "http",
      "url": "https://www.tasters.ch/mcp"
    }
  }
}

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.4.0LatestNov 4, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.