BART Real-Time Transit
REMOTE · BART-MCP.SRIVASTSH.WORKERS.DEV · SCANNED SEP 22
Real-time BART departures, trip planning, fares, stations, and advisories.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 354 tokens (~50/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BART Real-Time Transit MCP server?
BART Real-Time Transit is a hosted endpoint at https://bart-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 · bart-mcp.srivastsh.workers.dev
claude mcp add --transport http srivastsh-bart-mcp 'https://bart-mcp.srivastsh.workers.dev/mcp'
{
"mcpServers": {
"srivastsh-bart-mcp": {
"url": "https://bart-mcp.srivastsh.workers.dev/mcp"
}
}
} {
"servers": {
"srivastsh-bart-mcp": {
"type": "http",
"url": "https://bart-mcp.srivastsh.workers.dev/mcp"
}
}
} [mcp_servers.srivastsh-bart-mcp] url = "https://bart-mcp.srivastsh.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"srivastsh-bart-mcp": {
"type": "remote",
"url": "https://bart-mcp.srivastsh.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add srivastsh-bart-mcp --url 'https://bart-mcp.srivastsh.workers.dev/mcp' --transport streamable-http
mcp_servers:
srivastsh-bart-mcp:
url: "https://bart-mcp.srivastsh.workers.dev/mcp" {
"McpServers": {
"srivastsh-bart-mcp": {
"Transport": "http",
"Url": "https://bart-mcp.srivastsh.workers.dev/mcp"
}
}
} assistant mcp add srivastsh-bart-mcp -t streamable-http -u 'https://bart-mcp.srivastsh.workers.dev/mcp'
{
"mcpServers": {
"srivastsh-bart-mcp": {
"type": "http",
"url": "https://bart-mcp.srivastsh.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 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
- Tool “bart_advisories” now declares an output schema ▲ functional
- Tool “bart_departures” now declares an output schema ▲ functional
- Tool “bart_fare” now declares an output schema ▲ functional
- Tool “bart_station_lookup” now declares an output schema ▲ functional
- Tool “bart_stations” now declares an output schema ▲ functional
- Tool “bart_status_summary” now declares an output schema ▲ functional
- Tool “bart_trip” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.1.0 → 1.2.0 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.
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://bart-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 bart-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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bart-mcp.srivastsh.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://bart-mcp.srivastsh.workers.dev/mcp | Inconclusive | 405 |
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 →
bart_advisories BART Advisories ~27
Get current BART service advisories, delays, and elevator/escalator status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| advisories | array | yes | – |
No examples provided.
bart_departures BART Real-Time Departures ~80
Get real-time departures from a BART station. Args: - station: 4-letter abbreviation (e.g. EMBR, 24TH) - direction: Optional 'n' or 's'
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Direction filter |
| station | string | yes | Station code (e.g. EMBR, 24TH) |
| Name | Type | Req | Description |
|---|---|---|---|
| departures | array | yes | – |
No examples provided.
bart_fare BART Fare ~37
Get fare between two BART stations.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination station code |
| origin | string | yes | Origin station code |
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| fare | – | yes | – |
| origin | string | yes | – |
No examples provided.
bart_station_lookup Find BART Stations ~78
Search BART stations by name, city, address, or 4-letter station code.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city filter |
| limit | integer | – | Maximum matches to return |
| query | string | yes | Station name, city, address fragment, or code, e.g. Embarcadero, Oakland, EMBR |
| Name | Type | Req | Description |
|---|---|---|---|
| stations | array | yes | – |
No examples provided.
bart_stations List BART Stations ~32
List all BART stations with abbreviation codes and locations. Use this to look up station codes needed by other tools.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| stations | array | yes | – |
No examples provided.
bart_status_summary BART Status Summary ~26
Summarize current BART service status from advisories and real-time alert data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| advisories | array | yes | – |
| advisoryCount | number | yes | – |
| types | object | yes | – |
No examples provided.
bart_trip Plan BART Trip ~74
Plan a trip between two BART stations. Returns schedule, fares, and transfer info.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date MM/DD/YYYY |
| destination | string | yes | Destination station code |
| origin | string | yes | Origin station code |
| time | string | – | Departure time e.g. '5:30pm' |
| Name | Type | Req | Description |
|---|---|---|---|
| trips | array | yes | – |
No examples provided.
What is the BART Real-Time Transit MCP server?
BART Real-Time Transit is an MCP server listed in the public MCP registry as io.github.srivastsh/bart-mcp. Real-time BART departures, trip planning, fares, stations, and advisories. This page covers its hosted endpoint (https://bart-mcp.srivastsh.workers.dev/mcp).
Is the BART Real-Time Transit MCP server safe to use?
BART Real-Time Transit scores 81 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 BART Real-Time Transit MCP server expose?
BART Real-Time Transit exposes 7 tools: bart_stations, bart_station_lookup, bart_departures, bart_trip, bart_advisories, and 2 more. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.
Does the BART Real-Time Transit MCP server require authentication?
No. We connected to BART Real-Time Transit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BART Real-Time Transit MCP server still maintained?
BART 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.