Releases: cyanheads/transitland-mcp-server
Releases · cyanheads/transitland-mcp-server
Release list
v0.1.1: mcp-ts-core 0.12 adoption
mcp-ts-core 0.12 adoption
Adopts @cyanheads/mcp-ts-core ^0.12.3 (SDK v2): every HTTP endpoint serves protocol revision 2026-07-28 alongside 2025-era clients, tool inputs are strict — unknown argument keys are rejected by name — and advertised schemas move to JSON Schema 2020-12.
- Guard rejections (
no_filter,incomplete_point) classify as ValidationError (-32007) with the recovery hint on the wire instead of InvalidParams - Single-record lookups pass expectedStatuses [404], so absent IDs log at debug rather than error
- New smoke / integration / fuzz test tiers from the framework templates; TypeScript ^6.0.3 → ^7.0.2
- deps:
@cyanheads/mcp-ts-core^0.10.6 → ^0.12.3 (+ dev-dep refresh) - Bun 1.4.0 Docker images with cache mounts and --omit=peer; bunfig release-age hold + Socket scanner; .mcpb strips platform-specific natives; community health files; protocol docs and skills resync
v0.1.0: Initial release
Initial release
Transitland v2 registry MCP server — global GTFS, GTFS-Realtime, and GBFS transit data. Onestop IDs are the identifier spine; place-name geocoding is delegated to openstreetmap_geocode.
Added:
- 6 tools: transitland_find_operators, transitland_get_operator, transitland_find_feeds, transitland_find_routes, transitland_find_stops, transitland_get_departures
- 2 resources: transitland://operator/{onestop_id}, transitland://feed/{onestop_id}
- find_feeds surfaces fetch URLs, license terms (redistribution/commercial/derived/attribution as yes/no/unknown — never inferred), and freshness
- get_departures distinguishes live GTFS-Realtime predictions from static schedule per departure
- TransitlandService — direct HTTP client; discards the key-bearing meta.next URL, surfacing only the opaque integer cursor
STDIO or Streamable HTTP. 48 tests pass; bun run devcheck clean.