Samuelz Chauffeur Booking

io.github.samuelzcomPublished by GitHub account samuelzcomv1.1.0Updated Oct 24, 2026

Chauffeur price previews and consent-led offers for the provider's published service areas.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server that lets an assistant preview chauffeur prices and request consent-led offers for the provider's published service areas.

What you can do
Preview chauffeur service prices for the provider's published service areas. Request offers that are consent-led, so the customer agrees before an offer proceeds. No individual tools are listed, so exact operations are not documented.
When to use it
Useful when someone wants an assistant to check chauffeur pricing or start a consent-based offer for a trip within the provider's published service areas.
Requirements
A remote endpoint at the provider's platform API, reached over streamable HTTP. No packages, environment variables, headers or authentication are declared, so any account or sign-in requirements are undocumented.
Before you install
The server is operated by a third party and handles booking-related requests, so trip details may be sent to the provider. No authentication is declared, which makes access control and data handling unclear. Confirm pricing and offer terms with the provider before relying on them.

Installation

In SourceWeft

  1. Open Samuelz Chauffeur Booking in the dashboard and add it to a workspace.
  2. 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/io.github.samuelzcom%2Fchauffeur-booking/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.

{
  "mcpServers": {
    "samuelz-chauffeur-booking": {
      "type": "http",
      "url": "https://platform-api.samuelz.com/api/v1/mcp/chauffeur/samuelz-chauffeur"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.1.0LatestOct 24, 2026
  2. v1.0.0Sep 22, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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