Istanbul MCP
REMOTE · ISTANBULMCP-PRODUCTION.UP.RAILWAY.APP
Read-only Istanbul open city data: transport, parking, water, nearby services and datasets.
Available components
Last scanned (58 minutes ago)
Scores higher than 60% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Maps and Location
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.13 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 28 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://istanbulmcp-production.up.railway.app/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of istanbulmcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://istanbulmcp-production.up.railway.app/mcp/ | Unreachable | ||
| http (plaintext) | http://istanbulmcp-production.up.railway.app/mcp/ | HTTPS enforced |
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 →
istanbul_city_services_nearby Yakındaki WiFi ve kütüphaneler ~146
Summarize 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 a point. For Acıbadem, specify 'Acıbadem, Kadıköy' or 'Acıbadem, Üsküdar'. Not full address geocoding.
| Name | Type | Req | Description |
|---|---|---|---|
| district | – | – | – |
| lat | – | – | – |
| limit | – | – | – |
| lon | – | – | – |
| place | – | – | – |
| radius_m | integer | – | – |
No output schema declared.
No examples provided.
istanbul_datastore_query Sınırlı açık veri SQL sorgusu ~179
Run 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 server enforces an outer result limit (default 20, max 100) even if SQL omits LIMIT. Only resources configured in CKAN_SQL_ALLOWED_RESOURCE_IDS are available. Local query syntax and bounds: https://github.com/Batu1-1an/istanbulmcp/blob/main/docs/datastore-sql.md Source API: https://docs.ckan.org/en/latest/maintaining/datastore.html
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | – |
| resource_id | string | yes | – |
| sql | string | yes | – |
No output schema declared.
No examples provided.
istanbul_get_dataset İBB veri seti bilgileri ~29
Return metadata and resources for one IBB dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
No output schema declared.
No examples provided.
istanbul_get_resource_schema İBB kaynak kolonları ~29
Return DataStore field schema for a resource.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_id | string | yes | – |
No output schema declared.
No examples provided.
istanbul_gtfs_snapshot_status GTFS tarife anlık görüntü durumu ~75
Inspect 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 service.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_health İstanbul servis durumu ~16
Return Istanbul MCP service readiness.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
istanbul_market_schedule İstanbul pazar takvimi ~92
Return 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 link.
| Name | Type | Req | Description |
|---|---|---|---|
| day | – | – | – |
| district | – | – | – |
| limit | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_metro_accessibility_status Metro ekipman ve arıza durumu ~70
Return 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.
| Name | Type | Req | Description |
|---|---|---|---|
| equipment_type | – | – | – |
| limit | – | – | – |
| line | – | – | – |
| station | – | – | – |
No output schema declared.
No examples provided.
istanbul_mobility_nearby Yakındaki ulaşım seçenekleri ~127
Summarize 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'. Not address geocoding.
| Name | Type | Req | Description |
|---|---|---|---|
| district | – | – | – |
| lat | – | – | – |
| limit | – | – | – |
| lon | – | – | – |
| place | – | – | – |
| radius_m | integer | – | – |
No output schema declared.
No examples provided.
istanbul_nearby Yakındaki İstanbul hizmetleri ~192
Find 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 station locations only. Static layers return published locations, not live status. District lists have no distances. Pharmacy records include name, district, address, phone, map links, provenance and freshness; maps_search_url is address search, not a verified pin. Pharmacy duty-end times are not guaranteed. Card/social locations are static, not live operating status.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | – | – | – |
| district | – | – | – |
| kind | string | – | – |
| lat | – | – | – |
| limit | – | – | – |
| lon | – | – | – |
| radius_m | – | – | – |
| types | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_neighborhood_profile İstanbul mahalle profili ~44
Return a joined neighborhood profile from social, building, and earthquake scenario records.
| Name | Type | Req | Description |
|---|---|---|---|
| district | string | yes | – |
| limit | – | – | – |
| neighborhood | – | – | – |
No output schema declared.
No examples provided.
istanbul_next_departures Planlı GTFS durak kalkışları ~260
Search 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 the first automatically. Approximate spelling suggestions are labeled, not matches. Ask the user to select a candidate using name/map, then call with stop_id. stop_code identifies the published stop sign when present. stop_desc and platform_direction_text preserve source text; they are not inferred route directions. Missing metadata stays null; districts are not inferred. at is an ISO datetime with a UTC offset; omitted means now in Europe/Istanbul. The search covers 24 hours. stop_id and coordinates are mutually exclusive. line matches the published route short name. Times are scheduled, never live ETA, delays or proof of service. Outside-calendar queries are unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| at | – | – | – |
| lat | – | – | – |
| limit | – | – | – |
| line | – | – | – |
| lon | – | – | – |
| radius_m | integer | – | – |
| stop_id | – | – | – |
| stop_query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_query_resource İBB kaynak kayıtları ~79
Query 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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | – | – | – |
| limit | – | – | – |
| resource_id | string | yes | – |
No output schema declared.
No examples provided.
istanbul_search_datasets İBB veri seti arama ~37
Search the IBB open data catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| formats | – | – | – |
| limit | – | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
istanbul_traffic_status İstanbul trafik yoğunluğu ~19
Return Istanbul citywide traffic index.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_transit_line İETT hat bilgileri ve tarifesi ~80
Get 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| limit | – | – | – |
| line_code | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_transport_disruptions Ulaşım aksaklıkları ve duyurular ~45
Return current official disruptions and service announcements across supported transport operators.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | – |
| line | – | – | – |
| mode | – | – | – |
| operator | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
istanbul_water_status İSKİ su ve baraj durumu ~111
Get 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 restoration guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| dam_name | – | – | – |
| district | – | – | – |
| fault_number | – | – | – |
| kind | string | – | – |
| limit | – | – | – |
| min_occupancy | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| error | – | – | – |
| freshness | – | yes | – |
| geojson | – | – | – |
| limits | array | – | – |
| next_queries | array | – | – |
| ok | boolean | – | – |
| pagination | – | – | – |
| result_info | – | – | – |
| sources | array | – | – |
| summary | string | yes | – |
| warnings | array | – | – |
No examples provided.
How do I install the Istanbul MCP server?
Istanbul MCP is a hosted endpoint at https://istanbulmcp-production.up.railway.app/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 · istanbulmcp-production.up.railway.app
claude mcp add --transport http batu1-1an-istanbul-mcp 'https://istanbulmcp-production.up.railway.app/mcp/'
What is the Istanbul MCP server?
Istanbul MCP is listed in the public MCP registry as io.github.Batu1-1an/istanbul-mcp. Read-only Istanbul open city data: transport, parking, water, nearby services and datasets. This page covers its hosted endpoint (https://istanbulmcp-production.up.railway.app/mcp/).
Is the Istanbul MCP server safe to use?
Istanbul MCP scores 73 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 Istanbul MCP server expose?
Istanbul MCP exposes 18 tools: istanbul_health, istanbul_search_datasets, istanbul_get_dataset, istanbul_get_resource_schema, istanbul_query_resource, and 13 more. Their descriptions and schemas cost roughly 1,630 tokens of context every time the server is loaded.
Does the Istanbul MCP server require authentication?
Its publisher declares no required credentials for Istanbul MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Istanbul MCP server still maintained?
Istanbul MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.