Istanbul MCP

io.github.Batu1-1an/istanbul-mcp · v0.2.5 · data-and-databases

Istanbul MCP is healthy: it completed an MCP handshake in 582 ms and exposes 18 tools.

Read-only Istanbul open city data: transport, parking, water, nearby services and datasets.

Endpoint: https://istanbulmcp-production.up.railway.app/mcp/ (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count18
Latency582 ms
Last checked (UTC)2026-10-25T17:50:25.843Z

Health history

Checked (UTC)StatusLatencyError
2026-10-25T17:50:25.843ZHealthy582

Tools (18)

istanbul_healthReturn Istanbul MCP service readiness.
istanbul_search_datasetsSearch the IBB open data catalog.
istanbul_get_datasetReturn metadata and resources for one IBB dataset.
istanbul_get_resource_schemaReturn DataStore field schema for a resource.
istanbul_query_resourceQuery IBB CKAN DataStore records with guarded filters and limits. API reference: https://docs.ckan.org/en/latest/maintaining/datastore.html Uses datastore_search, not SQL; field names come from the resource schema.
istanbul_nearbyFind city services by kind and coordinates, or parking/pharmacy by district. bbox and types apply only to city_feature (parking, metro_station, air_quality_station, public_transport_stop, wifi, ev_charging, taxi_stand, market). air_quality includes latest readings; city_feature has stat
istanbul_traffic_statusReturn Istanbul citywide traffic index.
istanbul_water_statusGet ISKI active faults (district or fault_number) or dam occupancy. Dam filters apply only to dams; fault_number is exclusive with district. Nearby faults are provided by istanbul_nearby(kind="water_fault"). Results carry fallback freshness and approximate fault locations; no restoratio
istanbul_mobility_nearbySummarize mobility near a static place reference or coordinates. district (all 39 Istanbul districts) is exclusive with place/coordinates and returns parking only, without distances. District-only place names do the same. For Acıbadem specify 'Acıbadem, Kadıköy' or 'Acıbadem, Üsküdar'.
istanbul_city_services_nearbySummarize WiFi near a static reference point and district-level libraries/culture. district (all 39 Istanbul districts) is exclusive with place/coordinates; district-only place names also return district address lists, without WiFi or invented distances. Radius applies only to WiFi with
istanbul_neighborhood_profileReturn a joined neighborhood profile from social, building, and earthquake scenario records.
istanbul_transit_lineGet IETT line info, ordered stops or planned main-terminal departures. limit applies only to departures. This is not live intermediate-stop ETA. Cross-operator service notices are provided by istanbul_transport_disruptions.
istanbul_transport_disruptionsReturn current official disruptions and service announcements across supported transport operators.
istanbul_metro_accessibility_statusReturn official Metro İstanbul equipment/total counts and current equipment fault details, optionally filtered by line, station, or equipment type. This is not an end-to-end accessibility guarantee.
istanbul_datastore_queryRun a bounded SELECT over records from one allowlisted CKAN resource. SQLite dialect: use table records and published column names. GROUP BY and aggregates are supported; no writes, arbitrary functions or application DB. A complete bounded capture is required, never partial counts. The
istanbul_market_scheduleReturn the published weekly İBB market schedule, optionally by district/day. day accepts Turkish/English weekdays, today/yesterday/tomorrow, or an ISO date. Results are a static weekly schedule, not proof a market is open today; coordinates are source points and maps_url is a map search
istanbul_next_departuresSearch GTFS stop names or return published departures for selected stops. Use stop_query with limit only to discover stop_id candidates by name, including Turkish/ASCII spellings (Kadıköy/kadikoy). This mode returns stops, NOT departures. Same-name stops remain separate; never choose th
istanbul_gtfs_snapshot_statusInspect local GTFS load age, calendar validity, row counts and skipped rows. No upstream request or refresh is made. A missing or warming snapshot is unavailable, not an empty timetable. Cache age is not feed publication age; a loaded snapshot does not prove live arrivals or transport s