Live Times Transit
REMOTE · LIVEBUSTIMES.ORG · 2 COMPONENTS · SCANNED SEP 20
Read-only public transit departures, stop search, and city coverage for bus and train users.
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 894 tokens (~178/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Live Times Transit MCP server?
Live Times Transit is a hosted endpoint at https://livebustimes.org/api/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 · livebustimes.org
claude mcp add --transport http travelwhiz-ltd-live-times-transit 'https://livebustimes.org/api/mcp'
{
"mcpServers": {
"travelwhiz-ltd-live-times-transit": {
"url": "https://livebustimes.org/api/mcp"
}
}
} {
"servers": {
"travelwhiz-ltd-live-times-transit": {
"type": "http",
"url": "https://livebustimes.org/api/mcp"
}
}
} [mcp_servers.travelwhiz-ltd-live-times-transit] url = "https://livebustimes.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"travelwhiz-ltd-live-times-transit": {
"type": "remote",
"url": "https://livebustimes.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add travelwhiz-ltd-live-times-transit --url 'https://livebustimes.org/api/mcp' --transport streamable-http
mcp_servers:
travelwhiz-ltd-live-times-transit:
url: "https://livebustimes.org/api/mcp" {
"McpServers": {
"travelwhiz-ltd-live-times-transit": {
"Transport": "http",
"Url": "https://livebustimes.org/api/mcp"
}
}
} assistant mcp add travelwhiz-ltd-live-times-transit -t streamable-http -u 'https://livebustimes.org/api/mcp'
{
"mcpServers": {
"travelwhiz-ltd-live-times-transit": {
"type": "http",
"url": "https://livebustimes.org/api/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.
- 5 Sept 26 +49
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: fail → partial ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 4 Sept 26 −48
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://livebustimes.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=livebustimes.org | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f69d15e730f8232a13aabfc8fc3ef5fc |
| SANs: livebustimes.org, *.livebustimes.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of livebustimes.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| livebustimes.org. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://livebustimes.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://livebustimes.org/api/mcp | HTTPS enforced | 301 | https://livebustimes.org/api/mcp |
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 →
find_stops Find Stops ~208
Resolve a named place with Apple Maps when needed, then find nearby stops or stations so callers can pass a stop_id to get_departures. For ambiguous names, include near or country_code. If the user asks for a train, select a RAIL result.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | Two-letter ISO country code used to constrain Apple Maps geocoding, for example GB. |
| lat | number | – | Optional latitude used instead of Apple Maps geocoding. Must be supplied with lon. |
| locale | string | – | Optional BCP-47 locale, for example en-GB or fr-FR. |
| lon | number | – | Optional longitude used instead of Apple Maps geocoding. Must be supplied with lat. |
| near | string | – | Locality used to resolve the search origin, for example London, UK. Supply this or country_code when coordinates are unavailable. |
| query | string | yes | Stop or station search text, for example London Waterloo or Basingstoke. |
Structured output declared, but exposes no named fields.
No examples provided.
get_city_summary Get City Summary ~68
Return Live Bus Times and Live Train Times coverage metadata and canonical links for a supported city.
| Name | Type | Req | Description |
|---|---|---|---|
| city_id | string | yes | Canonical city ID, for example gb-london. |
| locale | string | – | Optional BCP-47 locale, for example en-GB or fr-FR. |
Structured output declared, but exposes no named fields.
No examples provided.
get_departures Get Stop Departures ~133
Return a Live Times departure board for a known canonical stop ID. Optionally filter by route pattern or by up to 5 destinations.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_by | string | – | Optional filter type. |
| filter_value | string | – | Required with filter_by. For DESTINATION, use one canonical stop ID, region-<id>, or up to 5 comma-separated values. |
| locale | string | – | Optional BCP-47 locale, for example en-GB or fr-FR. |
| stop_id | string | yes | Canonical Live Times stop ID, for example s-gcpvj0duq5-waterloo. |
Structured output declared, but exposes no named fields.
No examples provided.
plan_journey Plan a Journey ~250
Return compact step-by-step public transit directions between named places. Resolves names with Apple Maps and returns clarification candidates rather than guessing when a place is ambiguous.
| Name | Type | Req | Description |
|---|---|---|---|
| arrive_by | string | – | Optional ISO-8601 arrival datetime with explicit timezone offset. Do not combine with depart_at. |
| depart_at | string | – | Optional ISO-8601 departure datetime with explicit timezone offset. Do not combine with arrive_by. |
| destination | string | yes | Destination place name, address, landmark, or station. |
| destination_country_code | string | – | – |
| destination_near | string | – | Optional locality context for the destination. |
| destination_place_id | string | – | Optional Momego place ID selected from a previous clarification result. |
| locale | string | – | Optional BCP-47 locale, for example en-GB. |
| mode | string | – | – |
| num_results | integer | – | – |
| origin | string | yes | Origin place name, address, landmark, or station. |
| origin_country_code | string | – | – |
| origin_near | string | – | Optional locality context for the origin. |
| origin_place_id | string | – | Optional Momego place ID selected from a previous clarification result. |
Structured output declared, but exposes no named fields.
No examples provided.
search_places Search Place Suggestions ~119
Return up to 5 Apple Maps place candidates with Momego place IDs. Use this proactively when an origin or destination name is ambiguous, then pass the selected place ID to plan_journey.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | Optional two-letter ISO country code. |
| limit | integer | – | – |
| locale | string | – | Optional BCP-47 locale, for example en-GB. |
| near | string | – | Optional locality context, for example London, UK. |
| query | string | yes | Place, address, landmark, or station name. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Live Times Transit MCP server?
Live Times Transit is an MCP server listed in the public MCP registry as io.github.travelwhiz-ltd/live-times-transit. Read-only public transit departures, stop search, and city coverage for bus and train users. This page covers its hosted endpoint (https://livebustimes.org/api/mcp).
Is the Live Times Transit MCP server safe to use?
Live Times Transit scores 82 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 Live Times Transit MCP server expose?
Live Times Transit exposes 5 tools: get_departures, find_stops, search_places, plan_journey, get_city_summary. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.
Does the Live Times Transit MCP server require authentication?
No. We connected to Live Times Transit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Live Times Transit MCP server still maintained?
Live Times Transit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.