_ registry / mcp streamable-http · checked 7h ago

live-times-transit

https://livebustimes.org

Registry code: 56350a1c5d5eb2cf

api record

Read-only public transit tools from Momego. Use plan_journey for step-by-step directions between named places. Add locality or country context when it is known. If plan_journey returns clarification_required, ask the user to choose from the candidates and retry with the selected Place ID. Convert requested departure or arrival times to ISO-8601 with an explicit timezone offset; clarify when the timezone is uncertain. Use search_places proactively for ambiguous place names, find_stops before get_departures when a stop ID is unknown, and get_city_summary for coverage and links.

endpoint
https://livebustimes.org/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is live-times-transit live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is live-times-transit free to use?
Yes — the hub reached it with no key and no payment.
What tools does live-times-transit have?
5 tools: search_places, find_stops, plan_journey, get_city_summary, get_departures.
Is live-times-transit safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.3%· all time 99.3%

latency
128ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 274 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places travel & transport
used for
  • plan a public transit journey
  • find nearby transit stops
  • get a live departure board
  • search places by name
takes → gives
text, data → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_places reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "near": {
      "type": "string",
      "description": "Optional locality context, for example London, UK."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 5,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Place, address, landmark, or station name."
    },
    "locale": {
      "type": "string",
      "description": "Optional BCP-47 locale, for example en-GB."
    },
    "country_code": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "Optional two-letter ISO country code."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • find_stops reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "anyOf": [
    {
      "required": [
        "lat",
        "lon"
      ]
    },
    {
      "required": [
        "near"
      ]
    },
    {
      "required": [
        "country_code"
      ]
    }
  ],
  "required": [
    "query"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Optional latitude used instead of Apple Maps geocoding. Must be supplied with lon."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Optional longitude used instead of Apple Maps geocoding. Must be supplied with lat."
    },
    "near": {
      "type": "string",
      "description": "Locality used to resolve the search origin, for example London, UK. Supply this or country_code when coordinates are unavailable."
    },
    "query": {
      "type": "string",
      "description": "Stop or station search text, for example London Waterloo or Basingstoke."
    },
    "locale": {
      "type": "string",
      "description": "Optional BCP-47 locale, for example en-GB or fr-FR."
    },
    "country_code": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "Two-letter ISO country code used to constrain Apple Maps geocoding, for example GB."
    }
  },
  "additionalProperties": false
}
    arguments 56 lines
  • plan_journey reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "mode": {
      "enum": [
        "FASTEST",
        "BUS_ONLY",
        "RAIL_ONLY",
        "SUBWAY_ONLY",
        "STEP_FREE",
        "LESS_WALKING",
        "DIRECT",
        "CYCLE_TRANSIT",
        "DRIVE_TRANSIT"
      ],
      "type": "string",
      "default": "FASTEST"
    },
    "locale": {
      "type": "string",
      "description": "Optional BCP-47 locale, for example en-GB."
    },
    "origin": {
      "type": "string",
      "description": "Origin place name, address, landmark, or station."
    },
    "arrive_by": {
      "type": "string",
      "description": "Optional ISO-8601 arrival datetime with explicit timezone offset. Do not combine with depart_at."
    },
    "depart_at": {
      "type": "string",
      "description": "Optional ISO-8601 departure datetime with explicit timezone offset. Do not combine with arrive_by."
    },
    "destination": {
      "type": "string",
      "description": "Destination place name, address, landmark, or station."
    },
    "num_results": {
      "type": "integer",
      "default": 3,
      "maximum": 5,
      "minimum": 1
    },
    "origin_near": {
      "type": "string",
      "description": "Optional locality context for the origin."
    },
    "origin_place_id": {
      "type": "string",
      "description": "Optional Momego place ID selected from a previous clarification result."
    },
    "destination_near": {
      "type": "string",
      "description": "Optional locality context for the destination."
    },
    "origin_country_code": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$"
    },
    "destination_place_id": {
      "type": "string",
      "description": "Optional Momego place ID selected from a previous clarification result."
    },
    "destination_country_code": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$"
    }
  },
  "additionalProperties": false
}
    arguments 75 lines
  • get_city_summary reads unknown 7h ago

    Return Live Bus Times and Live Train Times coverage metadata and canonical links for a supported city.

    mcp-tool

    {
  "type": "object",
  "required": [
    "city_id"
  ],
  "properties": {
    "locale": {
      "type": "string",
      "description": "Optional BCP-47 locale, for example en-GB or fr-FR."
    },
    "city_id": {
      "type": "string",
      "description": "Canonical city ID, for example gb-london."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • get_departures reads unknown 7h ago

    Return a Live Times departure board for a known canonical stop ID. Optionally filter by route pattern or by up to 5 destinations.

    mcp-tool

    {
  "type": "object",
  "required": [
    "stop_id"
  ],
  "properties": {
    "locale": {
      "type": "string",
      "description": "Optional BCP-47 locale, for example en-GB or fr-FR."
    },
    "stop_id": {
      "type": "string",
      "description": "Canonical Live Times stop ID, for example s-gcpvj0duq5-waterloo."
    },
    "filter_by": {
      "enum": [
        "ROUTE_PATTERN",
        "DESTINATION"
      ],
      "type": "string",
      "description": "Optional filter type."
    },
    "filter_value": {
      "type": "string",
      "description": "Required with filter_by. For DESTINATION, use one canonical stop ID, region-<id>, or up to 5 comma-separated values."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 56350a1c5d5eb2cf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/56350a1c5d5eb2cf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/56350a1c5d5eb2cf/badge.svg)](https://brick.blue/agent/56350a1c5d5eb2cf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.