Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SF Muni Real-Time Transit

REMOTE · MUNI-MCP.SRIVASTSH.WORKERS.DEV · SCANNED SEP 22

Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules.

Available components

remote · muni-mcp.srivastsh.workers.dev 28
0 this week 28 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security71
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the SF Muni Real-Time Transit MCP server?

SF Muni Real-Time Transit is a hosted endpoint at https://muni-mcp.srivastsh.workers.dev/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.

remote · muni-mcp.srivastsh.workers.dev

# add to Claude Code
claude mcp add --transport http srivastsh-muni-mcp 'https://muni-mcp.srivastsh.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "srivastsh-muni-mcp": {
      "url": "https://muni-mcp.srivastsh.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "srivastsh-muni-mcp": {
      "type": "http",
      "url": "https://muni-mcp.srivastsh.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.srivastsh-muni-mcp]
url = "https://muni-mcp.srivastsh.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "srivastsh-muni-mcp": {
      "type": "remote",
      "url": "https://muni-mcp.srivastsh.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add srivastsh-muni-mcp --url 'https://muni-mcp.srivastsh.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  srivastsh-muni-mcp:
    url: "https://muni-mcp.srivastsh.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "srivastsh-muni-mcp": {
      "Transport": "http",
      "Url": "https://muni-mcp.srivastsh.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add srivastsh-muni-mcp -t streamable-http -u 'https://muni-mcp.srivastsh.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "srivastsh-muni-mcp": {
      "type": "http",
      "url": "https://muni-mcp.srivastsh.workers.dev/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 8 Aug 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: 0.40 → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: partial → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://muni-mcp.srivastsh.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=srivastsh.workers.dev CN=YE1,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA384 5ab99bb788591fbe7bdc4b5e465e57c4f4f
SANs: *.srivastsh.workers.dev, srivastsh.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of muni-mcp.srivastsh.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://muni-mcp.srivastsh.workers.dev/mcp Auth required 401
http (plaintext) http://muni-mcp.srivastsh.workers.dev/mcp Inconclusive 405
MCP tools · 11 exposed · ~727 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
muni_alerts ~48

Get current Muni service alerts, detours, and disruptions. Args: - operator_id: Optional (default 'SF')

NameTypeReqDescription
operator_idstring–Operator ID (default SF)

No output schema declared.

No examples provided.

muni_departures ~77

Get real-time departure predictions for a Muni stop. Args: - stop_code: The 5-digit stop code - operator_id: Optional (default 'SF')

NameTypeReqDescription
operator_idstring–Operator ID (default SF)
stop_codestringyesMuni stop code (e.g. '15731')

No output schema declared.

No examples provided.

muni_departures_by_route_stop ~77

Get real-time departures at a stop filtered to one Muni route/line.

NameTypeReqDescription
line_idstringyesRoute/line ID, e.g. N, 14, 38R
operator_idstring–Operator ID (default SF)
stop_codestringyesMuni stop code

No output schema declared.

No examples provided.

muni_line ~82

Get details for a specific Muni line including stops. Args: - line_id: Route/line ID (e.g. 'N', '14', '38R') - operator_id: Optional (default 'SF')

NameTypeReqDescription
line_idstringyesMuni line/route ID
operator_idstring–Operator ID (default SF)

No output schema declared.

No examples provided.

muni_nearby_stops ~76

Find Muni stops near a latitude/longitude point.

NameTypeReqDescription
latitudenumberyesLatitude
limitinteger–Maximum stops to return
longitudenumberyesLongitude
operator_idstring–Operator ID (default SF)
radius_milesnumber–Search radius in miles

No output schema declared.

No examples provided.

muni_routes ~54

List all SF Muni routes (bus, rail, cable car). Args: - operator_id: Optional operator ID (default 'SF' for Muni)

NameTypeReqDescription
operator_idstring–Operator ID (default SF)

No output schema declared.

No examples provided.

muni_schedule ~83

Get the timetable/schedule for a specific Muni line. Args: - line_id: Route/line ID (e.g. 'N', '14', '38R') - operator_id: Optional (default 'SF')

NameTypeReqDescription
line_idstringyesMuni line/route ID
operator_idstring–Operator ID (default SF)

No output schema declared.

No examples provided.

muni_status_summary ~36

Summarize current Muni service status from 511 service alerts.

NameTypeReqDescription
operator_idstring–Operator ID (default SF)

No output schema declared.

No examples provided.

muni_stop_search ~115

Search Muni stops by stop name, stop code, or route. Use this before muni_departures if you do not know the stop code.

NameTypeReqDescription
limitinteger–Maximum matches to return
line_idstring–Optional route/line filter, e.g. N, 14, 38R
operator_idstring–Operator ID (default SF)
querystringyesStop name, intersection, or stop code, e.g. Duboce, Van Ness, 15731

No output schema declared.

No examples provided.

muni_vehicles ~45

Get real-time GPS positions of Muni vehicles. Args: - operator_id: Optional (default 'SF')

NameTypeReqDescription
operator_idstring–Operator ID (default SF)

No output schema declared.

No examples provided.

transit_operators ~34

List all transit operators available in the 511 API (BART, Muni, Caltrain, AC Transit, etc.).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the SF Muni Real-Time Transit MCP server?

SF Muni Real-Time Transit is an MCP server listed in the public MCP registry as io.github.srivastsh/muni-mcp. Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules. This page covers its hosted endpoint (https://muni-mcp.srivastsh.workers.dev/mcp).

Is the SF Muni Real-Time Transit MCP server safe to use?

SF Muni Real-Time Transit scores 28 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 Muni Real-Time Transit MCP server expose?

SF Muni Real-Time Transit exposes 11 tools: transit_operators, muni_routes, muni_stop_search, muni_nearby_stops, muni_departures, and 6 more. Their descriptions and schemas cost roughly 727 tokens of context every time the server is loaded.

Does the SF Muni Real-Time Transit MCP server require authentication?

Yes. SF Muni Real-Time Transit asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the SF Muni Real-Time Transit MCP server still maintained?

SF Muni Real-Time Transit is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.