Baywheels Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

Bay Wheels bike share stations in the San Francisco Bay Area. No key required.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that gives an assistant access to Bay Wheels bike share station information in the San Francisco Bay Area, with no API key needed.

What you can do
  • Look up Bay Wheels bike share stations in the San Francisco Bay Area.
  • The manifest lists no individual tools, so the exact operations are not documented; expect station lookup and related bike share data.
  • Runs as a local process over stdio, so results come back directly into the assistant's conversation.
When to use it
Useful when you want an assistant to answer questions about Bay Wheels bike share stations in the San Francisco Bay Area, such as finding stations or checking bike share availability, without setting up an API key.
Requirements
Runs as a local process on the user's machine via stdio, installed from the npm package baywheels-mcp, so a Node.js runtime is needed. No authentication, environment variables or headers are declared. Desktop client only; not available as a web executable.
Before you install
The manifest declares no credentials and the description states no key is required. No tool list or README is available, so what data is fetched and whether anything is sent to third parties cannot be verified from the provided information.

Installation

In SourceWeft

  1. Open Baywheels Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

25% 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 days25 pts

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

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

  • License10 pts

    Declare a license in the repository or the registry entry.