Singapore LTA MCP Server

Created By
arjunkmrma year ago
MCP server to access Singapore's LTA data
Overview

what is Singapore LTA MCP Server?

The Singapore LTA MCP Server is an API server that provides real-time access to transportation information from Singapore's Land Transport Authority (LTA), including bus arrivals, traffic conditions, and train service updates.

how to use Singapore LTA MCP Server?

To use the server, install it via Smithery using the command: npx -y @smithery/cli install @arjunkmrm/mcp-sg-lta --client claude. You will also need to register for an API key from the LTA DataMall.

key features of Singapore LTA MCP Server?

  • Real-time bus arrival information
  • Updates on MRT/LRT station crowding levels
  • Alerts for train service disruptions
  • Availability of parking lots in real-time
  • Estimated travel times on expressway segments
  • Current road incidents updates

use cases of Singapore LTA MCP Server?

  1. Commuters checking bus arrival times before heading to the bus stop.
  2. Travelers monitoring crowd levels at MRT stations to avoid peak hours.
  3. Drivers looking for real-time traffic updates to plan their routes.
  4. Users checking carpark availability before arriving at their destination.

FAQ from Singapore LTA MCP Server?

  • How do I get an API key?

Register for an account on LTA DataMall, subscribe to the API services, and obtain your API key from the dashboard.

  • Is the server free to use?

Yes, the server is free to use, but you need to register for an API key.

  • How often is the data updated?

The data is updated at various intervals, with bus arrival times and traffic incidents updated every few minutes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
arjunkmrm
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago