# SF Bay Area Transit MCP (remote · mcp.riv.lc)

Plan San Francisco and Bay Area transit trips and check upcoming stop departures. Free, no API keys.

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.riv.lc`: 72/100 (this document), [markdown](https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp.md), [page](https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp)

## Channel facts

- Endpoint: `https://mcp.riv.lc/sf-transit/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 600 tokens (~120/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the SF Bay Area Transit MCP server?

SF Bay Area Transit MCP is a hosted endpoint at https://mcp.riv.lc/sf-transit/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http czekaj-sf-transit-mcp 'https://mcp.riv.lc/sf-transit/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "czekaj-sf-transit-mcp": {
      "url": "https://mcp.riv.lc/sf-transit/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "czekaj-sf-transit-mcp": {
      "type": "http",
      "url": "https://mcp.riv.lc/sf-transit/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.czekaj-sf-transit-mcp]
url = "https://mcp.riv.lc/sf-transit/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "czekaj-sf-transit-mcp": {
      "type": "remote",
      "url": "https://mcp.riv.lc/sf-transit/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add czekaj-sf-transit-mcp --url 'https://mcp.riv.lc/sf-transit/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  czekaj-sf-transit-mcp:
    url: "https://mcp.riv.lc/sf-transit/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "czekaj-sf-transit-mcp": {
      "Transport": "http",
      "Url": "https://mcp.riv.lc/sf-transit/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add czekaj-sf-transit-mcp -t streamable-http -u 'https://mcp.riv.lc/sf-transit/mcp'
```

### Other

```json
{
  "mcpServers": {
    "czekaj-sf-transit-mcp": {
      "type": "http",
      "url": "https://mcp.riv.lc/sf-transit/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +1)

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

### 2026-11-19 (score 71, +1)

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

### 2026-11-17 (score 70, +1)

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

### 2026-11-15 (score 69, +1)

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

### 2026-11-13 (score 68, +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.

### 2026-11-11 (score 67, +1)

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

### 2026-11-08 (score 66, +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.

### 2026-11-07 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `search_places` (~72 tokens)

Find Bay Area places

Find matching Bay Area addresses, landmarks, or transit stops and their map coordinates. Including the city helps distinguish places with the same name. Returns a list when more than one place matches. No API key. The search text is sent to Transitous.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `plan_trip` (~148 tokens)

Plan a Bay Area trip

Find complete trips with walking, transit, transfers, scheduled and predicted times, and total travel time. Use coordinates from the selected search result. Omit times for leaving now; otherwise supply departureTime OR arrivalTime with a UTC offset. Transit trips include walking to and from stops. Add walk or bicycle to modes to compare walking or cycling without transit. Coordinates are sent to Transitous. No API key.

Input parameters:

- `arrivalTime` (string)
- `departureTime` (string)
- `destination` (object, required)
- `limit` (integer)
- `maxTransfers` (integer)
- `modes` (array)
- `origin` (object, required)
- `wheelchair` (boolean)

### `get_stop_departures` (~96 tokens)

Next Bay Area departures

Show upcoming departures at a selected Bay Area transit stop, including live predictions where available, scheduled times, cancellations, and boarding restrictions. Use the stop ID and coordinates from a search_places STOP result or plan_trip stop. Omit departureTime for now. Stop ID and time are sent to Transitous. No API key.

Input parameters:

- `departureTime` (string)
- `limit` (integer)
- `stop` (object, required)

### `get_service_info` (~29 tokens)

Transit service information

Read the current time, available tools, data sources, and service limits without contacting a routing service.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 66
- 2026-11-09: 66
- 2026-11-08: 66
- 2026-11-07: 65
- 2026-11-06: 65

## Common questions

### What is the SF Bay Area Transit MCP server?

SF Bay Area Transit MCP is listed in the public MCP registry as io.github.czekaj/sf-transit-mcp. Plan San Francisco and Bay Area transit trips and check upcoming stop departures. Free, no API keys. This page covers its hosted endpoint (https://mcp.riv.lc/sf-transit/mcp).

### Is the SF Bay Area Transit MCP server safe to use?

SF Bay Area Transit MCP scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SF Bay Area Transit MCP server expose?

SF Bay Area Transit MCP exposes 4 tools: search_places, plan_trip, get_stop_departures, get_service_info. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.

### Does the SF Bay Area Transit MCP server require authentication?

No. We connected to SF Bay Area Transit MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SF Bay Area Transit MCP server still maintained?

SF Bay Area Transit MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SF Bay Area Transit MCP server?

VerifyMCP ran 13 checks on SF Bay Area Transit MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about SF Bay Area Transit MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.riv.lc/sf-transit/mcp
- Repository: https://github.com/czekaj/sf-transit-mcp
- Website: https://mcp.riv.lc/sf-transit
- Changelog RSS feed: https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/czekaj-sf-transit-mcp/sf-transit-mcp
